rabbitmq_delete_queue

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and does not mention irreversibility, prerequisites (e.g., requiring an active connection), failure modes when the queue does not exist, or the effect on bound exchanges or consumers.

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, front-loaded sentence with no fluff. It states the core purpose directly and efficiently, earning its place without any wasted words.

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 simplicity of the tool and high schema coverage, the description is minimally viable but lacks important context such as return behavior, error conditions, and any dependency on a prior connection (sibling rabbitmq_connect suggests this). The absence of an output schema and annotations increases the need for such context, which is not provided.

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 100%, so all parameters are already well-documented in the input schema. The tool description adds minimal semantic value beyond the schema; the only slight addition is the 'vhost' context, which is not needed for parameter interpretation.

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 from the vhost' clearly states a specific verb and resource, making it easy to distinguish from sibling tools like rabbitmq_purge_queue (which only clears messages) and rabbitmq_delete_exchange (which targets a different resource type).

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 explicit guidance is provided about when to use this tool vs. alternatives such as purge_queue. The presence of if_empty and if_unused parameters hints at safe deletion conditions, but the description does not state when deletion is appropriate or how it differs from purging or other operations.

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