delete_queue_by_id

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds little behavioral context beyond 'Delete Queue.' It does not explain side effects of the delete operation or what the query flags such as blocklist, remove_from_client, and skip_redownload actually do. There is no contradiction with the annotations, but the description also adds none of the missing operational detail.

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, front-loads the core action and endpoint, and presents the parameters as a clean list. There is no unnecessary prose, though the brevity is achieved by omitting semantic detail.

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 five-parameter destructive endpoint with 0% schema description coverage, the description is not complete enough. It gives the required id and endpoint for a minimal call, but it omits the meaning of all optional flags and provides no guidance for common scenarios such as removing from the client, blocklisting, or skipping redownload.

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%, so the description needed to clarify the five parameters, but it only lists their names and labels each as 'Path parameter' or 'Query parameter.' That path/query classification adds some value beyond the schema, but the meanings and behavioral consequences of blocklist, remove_from_client, skip_redownload, and change_category remain unexplained.

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 'Delete Queue' and gives the explicit DELETE /api/v3/queue/{id} endpoint, so the verb and resource are unmistakable. The required id path parameter signals this removes a single queue item, but the description does not explicitly distinguish it from the sibling delete_queue_bulk tool.

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 use this tool versus alternatives such as delete_queue_bulk or list_queue. The description only restates the endpoint and parameters, leaving the agent to infer usage from the tool name.

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