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

Annotations already declare destructiveHint=true and idempotentHint=true, so the risk profile is covered. The description adds genuinely new context: cancellation requires a signed-in Printdash account and triggers a sign-in prompt on printdash.io if absent. It does not say what state the request lands in or whether it is reversible.

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 sentences, both earning their place: the scoping constraint is front-loaded and the auth behavior follows. No filler or restatement of the title.

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?

An output schema exists, so return values need not be described, and annotations cover safety and idempotency. The auth gating is a useful addition; only the post-cancellation state of the request is left unstated.

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 coverage is 100% for the single `request` parameter, including the helpful note that it accepts the request number or the id from its link. The description adds no parameter-level detail, so the baseline 3 applies.

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 and resource ("Cancels a custom quote request") and narrows scope to those "still pending review", which distinguishes it from delete_quote or cancel_order. It stops short of naming the sibling that handles non-pending requests, so it is clear but not maximally differentiating.

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 phrase "still pending review" implies the applicable state, and the auth note tells the agent what happens when unauthenticated. There is no explicit when-not guidance or pointer to delete_quote/reject_order for other cases, leaving the agent to infer which sweep is appropriate.

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