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

Annotations already set destructiveHint=true, but the description goes further by explicitly warning 'DESTRUCTIVE', detailing what is deleted (all items, optionally filtered), and adding the user-confirmation requirement. This is valuable context beyond the annotation.

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?

Two concise, front-loaded sentences. Every word earns its place, starting with the crucial 'DESTRUCTIVE' warning, followed by the action and the safety confirmation.

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 simple destructive tool with two optional parameters and no output schema, the description covers purpose, parameter semantics, and the key safety requirement. It is complete enough for an agent to invoke correctly.

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 schema description coverage at 0%, the description explains both parameters: 'group' and 'done-only' as optional filters. This adds meaning beyond the raw schema, though it does not elaborate on what 'group' refers to in detail.

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 all items from the queue' with a specific verb and resource. It distinguishes itself from per-item queue tools like remove_from_queue by indicating bulk deletion, and optional filters for group or done-only provide clear scope.

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?

It provides clear context for when to use the tool (deleting all or filtered items) and explicitly instructs 'Confirm with the user before calling.' It does not explicitly name alternative tools for individual removal, but the scope is implicit enough.

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