manage_queue

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

Beyond annotations (destructiveHint=true), description details that clear/delete/interrupt discard queued work, and 'free' optionally unloads models. No contradiction; adds essential behavior context.

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 succinct sentences: first states purpose and lists actions, second warns about side effects. Every sentence is necessary and well-structured, front-loading key info.

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?

Covers all 5 actions, parameter usage, and destructive consequences. Output schema exists so return format is not needed. Complete for a tool with multiple destructive operations.

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 coverage, description fully explains each action and the meaning of 'unload_models'. It clarifies that 'prompt_ids' applies to 'delete'. Adds all meaning absent from schema.

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 it manages the run queue with specific actions (status, interrupt, clear, delete, free). It distinguishes from sibling tools by focusing exclusively on queue operations.

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?

Explicitly advises caution: 'clear/delete/interrupt discard other queued work - make sure that's what the user wants.' Guides appropriate use by flagging destructive actions.

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