deleteConnection

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

The description discloses that the tool performs a deletion (destructive action), but without annotations, it fails to detail side effects (e.g., permanent removal, impact on active sessions) or any required 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?

The description is a single short sentence with no unnecessary words, but it is too brief to be fully informative. It sacrifices completeness for brevity.

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 no output schema, no annotations, and a single parameter, the description should provide more context about return values, error handling, and where to find connectionId. It is insufficient for an agent to use correctly without external knowledge.

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?

The single parameter 'connectionId' is not described. With 0% schema description coverage, the description should explain what the ID represents and how to obtain it, but it provides no additional context beyond the parameter name.

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 action ('Deletes') and the resource ('a saved SSH connection'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools like getConnection or listConnections.

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 guidance is provided on when to use this tool versus alternatives (e.g., disconnect, closeTunnel). There is no mention of prerequisites, such as needing an active connection or the consequences of deletion.

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