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

Adds substantial context beyond the annotations: the call itself is non-mutating, it returns a preview plus a confirmation link, and only the merchant can complete the action. This reconciles the flow with destructiveHint=true since the destruction happens later, though the description does not say what the preview contains, whether the confirmation link expires, or what other data (e.g. products in the category) is affected.

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 behavioral sentences are tight and front-loaded, but the stray "Money is integer minor units (cents)" line is pure noise for a tool with no monetary parameter and reads as copy-paste from another definition. Removing it would leave a clean three-sentence definition.

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 single-parameter tool with no output schema, the description covers the critical surprises: no immediate side effect, preview return, confirmation-link step, and merchant-only authorization. It is only mildly incomplete on what the preview reports and whether the destructive action is attributable to this call at all.

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% and the single parameter's description already covers id/handle/title lookup forms, so the baseline is 3. The one parameter-related sentence in the description, "Money is integer minor units (cents)," is irrelevant to this tool and adds no meaning about the collection argument.

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 ("Delete a category") that cleanly separates it from collections_create, collections_edit, and collections_add_products. It does not name or contrast any sibling explicitly, and the word "Delete" is slightly at odds with the preview-only behavior described later, so it stops short of a 5.

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 description implies usage through the two-step workflow ("returns a preview... Only the merchant, on that page, can make it happen"), which tells the agent this is an initiation step, not a final deletion. However, it never states when to reach for this versus alternatives such as collections_edit, nor any prerequisite about being in a merchant-authenticated session.

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