delete-queue

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

The description only repeats the tool's name and is consistent with the annotation 'readOnlyHint: false', indicating a destructive write. However, it fails to add any behavioral context beyond what annotations already provide, such as whether the queue must be empty, whether it's reversible, or what happens to bindings.

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 concise at three words, but this sacrifices essential information. It is not appropriately sized for the tool's complexity; a single sentence of this length qualifies as under-specification rather than efficient conciseness.

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 lack of output schema and the simplicity of the parameters, the description should explain the effect of deletion (e.g., whether it's immediate, if messages are lost, if bindings are removed). The current description leaves critical questions unanswered, making it incomplete for correct invocation.

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 0% description coverage with two required parameters ('vhost' and 'name'), and the description does not mention or explain these parameters at all. The agent has no guidance on valid values or constraints, making it impossible to invoke the tool correctly without external knowledge.

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 'Delete a queue' clearly states the verb 'Delete' and the resource 'queue', making the immediate purpose obvious. However, it does not distinguish this tool from sibling tools like 'purge-queue' or 'pause-queue', which could be confused without additional 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?

No guidance is provided on when to use this tool versus alternatives such as 'purge-queue' (which removes messages but retains the queue) or other delete tools. The agent gets no context about prerequisites, typical use cases, or when this tool is inappropriate.

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