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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is largely covered. The description adds concrete behavioral detail beyond the annotations by stating the removal is permanent and irreversible, which is exactly the context an agent needs before calling a destructive tool. It omits idempotency and any auth requirements, keeping it short of a 5.

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?

Three short sentences, front-loaded with the action and keyed resource, followed by the irreversible-warning and the alternative. Every sentence earns its place with no padding.

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 single-parameter destructive tool with full annotation coverage, the definition supplies the action, required input, irreversibility, and an alternative for reads. The only small gap is that it doesn't say what the call returns, though with no output schema this is a minor omission.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents 'id' fully ('The ID of the connection to remove'). The description merely restates that the ID is required, adding no format or constraint detail beyond the schema. 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?

States a specific verb and resource (delete a connection) plus the keying mechanism (by its ID). It is clearly distinguishable from sibling mutators like remove_unified_environment or remove_unified_webhook, since the resource is named explicitly.

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?

Gives the deletion context and names a sibling (get_unified_connection) for retrieval, which helps routing. However, it doesn't contrast with update_unified_connection (the non-destructive modification path) or state prerequisites/conditions for deletion, so the when-not guidance is only partial.

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