delete_queue

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds two genuinely useful behavioral constraints beyond the annotations: the empty-queue precondition and the permission requirement. It does not say whether the deletion is reversible or what happens to associated tags/fields, keeping it below 5.

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 short sentences, zero filler, with the destructive action and its precondition front-loaded before the permission note.

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 tool with no output schema, the description covers the essential call-time concerns: emptiness precondition and authorization. It omits any mention of the required confirm flag or irreversibility, which would help an agent avoid an accidental confirmed deletion.

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 only 50%: only the 'confirm' parameter is documented in the schema, while queueId has no description anywhere. The description adds no parameter-level meaning, so it fails to compensate for the coverage gap.

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?

States a specific verb (Delete) and resource (queue), plus a scoping condition (only when empty of issues). It is distinguishable from neighboring delete tools like delete_queue_tag and delete_queue_version, though it does not name an alternative explicitly.

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?

Gives a clear precondition (queue must be empty of issues) and an authorization rule (owner or Tracker admin). It does not mention restore_queue as the recovery path or any alternative tool, so it falls short of a 5.

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