send_input

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

With no annotations, the description is the sole source of behavioral information. It states the action but does not disclose prerequisites (e.g., session must be active), side effects, how session_type affects behavior, or whether output is captured. This lack of context is a significant gap for a tool that interacts with sessions.

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 a single, direct sentence that is front-loaded and free of fluff. It is appropriately concise for a simple action, though it sacrifices necessary detail. The sentence earns its place but could be enriched without harming conciseness.

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?

The description covers the basic purpose but is insufficient for a 3-parameter tool with no annotations or output schema. It does not explain session_type, how to identify or select sessions, or expected behavior after sending input, making it incomplete for reliable invocation.

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?

The description provides some meaning by mapping 'text input' to input_text and 'active interactive session' to session_id. However, session_type is completely unexplained, and with 0% schema description coverage, the description does not compensate for the missing parameter documentation, leaving the agent uncertain about the optional parameter's role.

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 uses the specific verb 'send' with the resource 'text input' to 'any active interactive session,' clearly stating the action and target. However, it does not explicitly distinguish from sibling tools like exec_stream or ssh_session_command, which also interact with sessions, so it earns a 4 rather than 5.

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?

No guidance is provided about when to use this tool versus alternatives. There are no explicit usage conditions, exclusions, or references to other tools like exec_stream or session-specific commands, leaving the agent without decision-making support.

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