refactor: shorten tool descriptions to focus on when-to-use instead of how-to-use

[danieliyahu1]

Problem

The 5 tool description files (spawn.txt, read.txt, write.txt, list.txt, kill.txt) contained verbose usage instructions, parameter docs, and examples — 171 lines total. The AI agent doesn't need to re-read tutorial material on every turn; the Zod parameter schemas already describe each parameter.

More importantly, the descriptions gave the agent no guidance on when to choose pty_spawn over the built-in bash tool, forcing users to use the magic keyword "session" to trigger the right behavior.

Changes

All 5 files reduced from 171 lines to 10 lines total:

• spawn.txt — now leads with explicit decision criteria: when to use pty_spawn vs the built-in bash tool
• read.txt, write.txt, list.txt, kill.txt — trimmed to 1-3 lines focused purely on tool purpose

Why

The tool() function in the plugin SDK only has a single description: string field — there is no separate instructions or notes field. All communication about the tool goes through this one string. These descriptions should tell the agent what the tool is and when to use it, not how it works under the hood.

Before/After

File	Before	After
spawn.txt	52 lines	5 lines
read.txt	39 lines	3 lines
write.txt	28 lines	3 lines
list.txt	22 lines	1 line
kill.txt	25 lines	3 lines