delete-exchange

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

The description 'Delete an exchange' aligns with the readOnlyHint=false annotation. However, it adds no additional behavioral context, such as what happens to bindings, permission requirements, or whether the operation is reversible. The annotation already communicates the non-read-only nature, leaving little extra value from the description.

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 extremely brief—a single sentence. It is front-loaded but lacks detail. While concise, it sacrifices informative value, which proper conciseness should balance.

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 low complexity (2 simple params, no output schema), the description should cover operational details like action irreversibility or error conditions. It fails to do so, leaving the agent underinformed.

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 0%, and the description does not explain the two required parameters (vhost and name). The agent receives no help on valid values, constraints, or semantics beyond parameter names.

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 (delete) and the resource (an exchange). It distinguishes the tool as a delete operation among siblings like 'delete-queue' or 'delete-binding-*', but does not further differentiate by specifying scope or conditions.

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. There are no mentions of prerequisites, side effects, or when not to use it.

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