delete_connection

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's '🔴 DESTRUCTIVE · deletes data' and 'Confirm with the user' reinforce but do not add significant behavioral info beyond the annotations. The description could mention permanence or side effects but does not.

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 repetitive: 'Delete a connection' appears twice, followed by 'Deletes a record' and 'Delete an existing connection resource.' It contains redundant lines that could be condensed into a single clear sentence. The structure is not concise.

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 the tool's simplicity (one required param, no output schema) and annotations that cover safety, the description is adequate. However, it misses useful context like idempotency (though annotations indicate it) and potential side effects of deletion.

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 coverage is 100%, and the schema description for 'id' is adequate. The tool description does not add any additional meaning about the parameter beyond what the schema already provides.

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 it deletes a connection resource, using specific verb and resource. It differentiates from siblings by being explicitly for 'connections', not other entities. However, it lacks detail on what a connection is in this context.

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 provides a usage guideline: 'Confirm with the user before calling.' This gives a safety cue. However, it does not specify when to use this tool versus other delete tools (e.g., delete_variable), nor does it exclude use cases or suggest alternatives.

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