delete-connection

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

Annotations indicate readOnlyHint=false, meaning it's a mutation. The description adds no further behavioral details such as consequences on related entities (e.g., channels), required permissions, or whether the operation is reversible. Without annotations, the burden would be higher, but here the description provides minimal additional value.

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 sentence, which is concise, but it lacks structure and is too brief to convey necessary details. It earns its place but could be improved without adding bloat.

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 and low annotation detail, the description is incomplete. It does not explain return values, error conditions, or side effects. For a deletion tool, more context is needed for safe and correct use.

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 input schema has 2 parameters (name, reason) with 0% description coverage in the schema. The description does not mention any parameter semantics, leaving the agent to infer from parameter names alone. This is insufficient, especially for the optional 'reason' parameter.

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 'Close a specific connection' clearly indicates the action (close/delete) and the resource (connection). It is specific enough to understand the tool's basic function, but it does not differentiate from sibling tools like delete-stream-connection or other delete 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?

There is no guidance on when to use this tool versus alternatives. No context about prerequisites, when not to use, or comparison with other deletion tools (e.g., delete-stream-connection, delete-binding-*) is provided.

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