ssh_execute

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

The description adds details about automatic connection reuse, which is beyond annotations. It aligns with destructiveHint=true (command execution can modify server state). No contradictions found.

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, front-loads the purpose, and includes useful examples. Every sentence adds value, though the phrase 'Connections are established automatically and reused' could be slightly more precise.

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 the tool's complexity (3 parameters, output schema exists), the description adequately covers execution behavior, parameter roles, and connection management. No gaps remain for the agent.

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 100%, and the description does not add significant additional meaning beyond what is in the parameter descriptions (server_name, command, timeout). The examples illustrate usage but do not deepen semantic understanding.

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 verb 'Execute' and the resource 'command on a remote SSH server', with specific details on returning stdout, stderr, and exit code. It distinguishes from sibling tools that focus on file operations.

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 provides examples but does not explicitly state when to use this tool versus alternatives like ssh_read_file, nor does it include when-not-to-use guidance. Usage is implied through context.

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