delete_queue_bulk

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description adds little beyond restating the destructive delete operation. It does not explain what the bulk deletion does to queue items, whether removal from client/blocklisting are permanent, or what side effects occur.

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 compact and well-structured: a one-line summary, endpoint, and an args list. There is no filler, though the brevity comes at the cost of substantive explanation.

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 destructive bulk operation with five undocumented parameters, this description is not sufficient for an agent to understand the effects or invoke it confidently. The output schema and annotations cover some metadata, but the key behavioral and parameter context is missing.

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?

With 0% schema description coverage, the description was expected to explain the parameters, but it only labels the query params as 'Query parameter' with no meaning. The body parameter gets useful advice to read the matching GET or /schema endpoint, but remove_from_client, blocklist, skip_redownload, and change_category remain semantically opaque.

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 states the action and resource clearly ('Delete Queue' with the DELETE endpoint), so an agent knows it performs bulk queue deletion. It does not explicitly contrast with delete_queue_by_id, but the endpoint and name make the bulk scope apparent.

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?

There is no guidance about when to choose this tool over delete_queue_by_id or other queue-related operations. The only contextual hint is indirectly provided by the endpoint and sibling names, but the description never states conditions, prerequisites, or alternatives.

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