pty_send_command

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries full burden. It discloses session creation/reconnection, WebSocket data plane usage, and the idle_timeout/max_wait completion logic. It does not cover error handling or edge cases, but the output schema likely addresses return structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: purpose, process, guidance. Each sentence earns its place, with the most important information front-loaded. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool with an output schema, the description covers purpose, lifecycle, timing behavior, and alternatives. It leaves some edge-case behavior (e.g., errors, exit codes) unspecified, but the existence of an output schema mitigates the need to describe return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds semantic depth by explaining that session_name triggers creation/reconnection and how idle_timeout and max_wait control read termination, going beyond the parameters' own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Opening sentence states 'Send a command to an interactive PTY session and capture its output' – a specific verb and resource. It further distinguishes itself from siblings by explicitly contrasting with execute_command in the final sentence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: 'Prefer execute_command for non-interactive commands; use this for TTY-aware programs (REPLs, TUIs, interactive shells).' This names the alternative and gives concrete usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.