send_line

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

With no annotations, description bears full burden. It discloses that after sending line + '\n', the tool drains PTY bytes until quiescence or deadline. It also specifies deadline_s maximum of 300 seconds. No contradictions.

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?

The description is concise (approximately 150 words) and well-structured: action, prerequisite, behavior, constraint, example pattern. No superfluous information.

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?

Given 3 parameters and no output schema or annotations, the description covers behavior well but lacks explanation of return values or error conditions. For a tool that drains bytes, it's plausible but incomplete.

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 low (33%). The description adds meaning for 'line' (sent with newline) and 'deadline_s' (max 300, total budget). However, it does not fully compensate for all parameters; session_id is just a required field. Baseline 3 is appropriate.

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?

The description clearly states the action: 'Send one newline-terminated line to a stateful PTY session.' It specifies the verb 'send', resource 'line', and context 'stateful PTY session', distinguishing it from siblings like send_text or send_control.

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?

Explicitly states prerequisite: 'Requires an existing session created via create_session(session_id, cwd).' Provides a common SSH pattern as usage example, aiding when to use. Does not explicitly state when not to use, but pattern implies context.

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