Delete an SSH key

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

With no annotations, the description carries the burden and does well by warning the operation is 'destructive' and requires 'confirm true'. It does not explain idempotency, error behavior for invalid IDs, or consequences beyond deletion, but the critical safety warning is present.

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?

Two concise sentences that front-load the core action and immediately follow with critical safety context. No waste, every word earns its place.

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 2-param deletion tool with no output schema and no annotations, the description covers the essential safety warning and parameter requirement. It lacks details on failure modes or idempotency, but those are not strictly necessary for correct invocation.

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 50%: 'id' is documented in the schema, but 'confirm' has no schema description. The description compensates by mentioning 'confirm true', adding meaning beyond the schema for that parameter. Baseline 3 is appropriate given the mixed coverage.

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?

States a specific verb (Delete) and resource (SSH key), matching the title exactly. It is clearly distinguishable from sibling cloud_create_ssh_key and cloud_list_ssh_keys without opening the schema.

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 does not explicitly state when to use this tool versus alternatives or prerequisites like needing an existing key ID. However, the operation is straightforward and the required 'confirm' flag provides some implicit guidance on the destructive intent.

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