send_text

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

In the absence of annotations, the description discloses key behavioral traits: it drains PTY bytes until quiescence or deadline, and specifies the default quiescence timeout and deadline_s maximum. This goes beyond a simple 'send' action, though it could mention potential error cases.

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 extremely concise with three sentences: primary action, prerequisite, and behavioral detail. Every sentence adds unique information, and the structure is logical and front-loaded.

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 tool with no output schema, the description covers the main action, prerequisites, and behavioral details. It lacks explicit mention of return values or error handling, but the core functionality is well described.

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 description coverage is low (33%), but the description adds value for 'text' (raw, no newline) and explains how deadline_s is used. However, it does not describe the session_id parameter beyond the prerequisite, leaving some meaning to be inferred.

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 raw text', the resource 'stateful PTY session', and a key distinction 'without adding a newline', which differentiates it from sibling tools like send_line (which likely adds a newline).

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?

The description explicitly notes the prerequisite of an existing session via create_session(), and describes the behavior after sending (draining until silence or deadline). It does not explicitly state when not to use or alternatives, but the context is clear enough for an AI agent to infer appropriate usage.

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