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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say what cancellation does to the queue item, whether it is reversible, what permissions are needed, or how expectedVersion/idempotencyKey govern retries. 'Privacy-filtered project metadata' is opaque rather than informative.

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?

A single short sentence with no bloat, so nothing needs trimming. However, brevity here reflects under-specification rather than tight, front-loaded information — the one sentence raises questions instead of answering them.

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?

This is a destructive, version-guarded, idempotency-keyed mutation with no output schema, and the description never explains the outcome of the operation or its relationship to the update/cancel siblings. Given the complexity signalled by 6 parameters, a required idempotencyKey, and expectedVersion concurrency control, the description is materially incomplete.

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%, so the schema already carries full parameter semantics (idempotencyKey retry rules, expectedVersion conflict behavior, queueItemId prefix requirement). The description adds no parameter-level meaning, so the baseline of 3 applies. Note the sessionId/executionId schema descriptions are duplicated from projectId, but that is a schema issue, not a description one.

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 name says 'cancel' but the description says 'Update hosted cancel queue item', so the verb and the actual effect are left ambiguous — an agent cannot tell whether this cancels or merely edits the item. The resource is named but there is no differentiation from close siblings like update_queue_item, cancel_queue_type, or preview_queue_type_cancel. The phrase 'using privacy-filtered project metadata' adds opacity rather than clarity.

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 when-to-use guidance, no prerequisites, and no mention of alternatives despite several directly competing siblings (update_queue_item for edits, cancel_queue_type for type-level cancels, list_queue_items for discovery). The agent is left to infer everything from the name.

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