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

Annotations already declare destructiveHint=true, and the description adds that the item 'never executes', implying permanence. It also discloses the return format and workflow, providing behavioral context beyond the annotation. No contradiction with annotations.

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 structured with clear sections, but it includes extraneous content: a generic Chinese trigger sentence about querying/running/stopping/exporting data that is not specific to this destructive tool, and vague exclusions about 'internal worker-version or internal-detail APIs'. These do not earn their place and may confuse the agent.

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?

Despite no output schema, the description provides the return format (JSON with results[]: {queue_ref, success, error?}) and a workflow prerequisite (call after list_run_queue_items). It covers the essential context for safe usage, though the irrelevant Chinese trigger slightly detracts. Overall, quite complete for a simple removal tool.

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 100%, with both parameters already documented. The description adds only minor context by mentioning 'queue_id' and confirming it from list_run_queue_items, which is already in the schema. Given high schema coverage, baseline 3 is appropriate.

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 the verb and resource: 'Release (remove) a single CoreClaw Run Queue item so it never executes.' It distinguishes from the sibling tool 'release_run_queue_items' by noting the singular version uses the queue_ref in the path. This is specific and unambiguous.

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?

The 'WHEN TO USE' section explicitly says to use when removing one queued run by queue_id and contrasts it with the plural version. 'WHEN NOT TO USE' gives exclusions (public search, internal APIs), and WORKFLOW instructs to call after list_run_queue_items to confirm the queue_id. This provides clear guidance on when and how to use it.

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