ssh

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

Annotations indicate write capability (readOnlyHint=false), but the description does not disclose that it executes remote commands, returns output, or potential side effects. Missing details on authentication handling.

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, no bureaucratic text. However, it could be slightly expanded to include return values without losing 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?

No output schema; description omits what the tool returns (stdout, stderr, exit code). Also lacks details on timeout, error handling, or authentication flow, making it incomplete for a command execution tool.

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?

Input schema has 100% coverage with descriptions. The description adds no additional meaning beyond the schema, hence baseline score.

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 'Connect to a target via SSH' clearly states the verb and resource, distinguishing it from sibling tools like scp (file transfer) or telnet (different protocol).

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 guidance on when to use this tool versus alternatives like scp or telnet. It does not mention prerequisites or conditions under which SSH is appropriate.

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