ssh_send_input

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

No annotations provided and description is minimal. Does not disclose required preconditions (e.g., active interactive session), behavior on invalid session, or side effects.

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?

One concise sentence, front-loaded with verb and resource, no filler. Efficient for an agent to parse.

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 simple tool with 2 required params and no output schema, description is minimally adequate but could mention prerequisite of an existing interactive session.

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 covers both parameters with descriptions; description adds examples (如密码、命令等) but doesn't significantly enhance understanding beyond schema. Baseline score 3.

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?

Clearly states it sends input (password, commands) to an interactive session, distinguishing from siblings like ssh_execute which execute commands non-interactively.

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 explicit when-to-use or alternatives. Implies use for interactive sessions needing input but lacks guidance on preconditions or comparison with ssh_start_interactive or ssh_execute.

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