ssh_generate_key

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

With no annotations, the description must carry behavioral disclosure. It mentions optional file saving, but fails to state whether keys are returned when no path is given, whether existing files are overwritten, or security-related behaviors like passphrases and file permissions.

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?

Single sentence with no filler, front-loading the action and resource, then compactly mentioning options. Every clause adds information.

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 tool with no output schema, no annotations, and 4 optional parameters, the description omits critical operational details: what the response contains, what happens if save_path is omitted, and whether the generated key is available immediately or only on disk.

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 already documents all 4 parameters (100% coverage), so the description adds little beyond naming RSA/Ed25519 and the optional save path. Baseline 3 applies.

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?

Description clearly states a specific verb ('Generate'), a specific resource ('new SSH key pair'), supported algorithms (RSA or Ed25519), and purpose (authentication). It is clearly distinct from sibling tools focused on sessions, connections, execution, and file transfer.

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 phrase 'for secure key-based authentication' implies use when creating SSH credentials, but there is no explicit guidance on when to use this tool over alternatives, prerequisites, or exclusions.

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