delete-binding-exchange-exchange

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

The description conveys a destructive operation but lacks additional behavioral context such as authentication requirements, side effects, or idempotency. Annotations indicate readOnlyHint=false, which aligns, but no extra insight is given.

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 concise sentence, but for a tool with four required parameters and no structure, it is under-specified. A brief sentence is acceptable but not optimally structured.

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 the complexity of a delete operation, the description lacks critical context such as error handling, idempotency behavior, or effects on message flow. Completeness is inadequate.

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 any of the four required parameters (vhost, source, destination, props). This provides zero added value over the raw schema.

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 resource (a binding from one exchange to another), distinguishing it from sibling tools like delete-binding-exchange-queue.

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 on when to use this tool versus alternatives like delete-binding-exchange-queue. No prerequisites or context for usage provided.

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