ssh_execute

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states it executes and returns output, but does not mention potential side effects (e.g., session state changes), blocking behavior, security considerations, or that commands may be destructive. The timeout parameter hints at behavior but is not explained.

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 sentence that front-loads the verb and resource. It contains no redundant words and is efficiently structured for quick parsing.

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?

Despite having an output schema and three parameters, the description lacks critical context: no explanation of return value format (though output schema may cover this), no mention of error handling, timeouts beyond parameter, or prerequisites. With no annotations, the description is insufficient for an agent to fully understand the behavior.

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 100%, so the baseline is 3. The description does not add meaning beyond the schema: the parameter descriptions in the input schema already explain 'command', 'timeout', and 'session_id' sufficiently. The overall description only restates the tool purpose without enriching parameter semantics.

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 it executes commands in an established SSH session and returns output. The verb 'execute' and resource 'command in SSH session' are specific, and it helps distinguish from sibling tools like ssh_connect (creates sessions) and ssh_close (closes sessions).

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 implies usage after establishing a session ('in an established SSH session'), but it does not explicitly state when to use this tool versus alternatives like ssh_read_output, nor does it provide when-not-to-use or alternative guidance. The context is understood but not explicit.

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