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

Annotations already flag destructiveHint=true, but the description goes well beyond them: no undo, products survive and simply lose the category (orphaned products become uncategorised), and two hard refusal conditions are disclosed. This is unusually rich consequence disclosure for a delete operation.

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?

Front-loads the action, then the id constraint, then the irreversible-confirmation warning, then the side effects and refusals. Dense but every clause carries decision-relevant information; nothing is padding.

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 destructive tool with no output schema, the description covers everything an agent must know: how to obtain the id, that confirmation is required, that the action is irreversible, what happens to dependent products, and the two blocking conditions.

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 schema already says 'Category id from get_categories — not a name', so the baseline is 3. The description reinforces the constraint ('takes the category id ONLY ... never guess'), adding a procurement instruction rather than new syntax, so it sits just above baseline.

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 is immediately distinguishable from hub_create_category, hub_update_category, and the other hub_delete_* siblings. The scope is further pinned down by describing exactly what is and is not removed.

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?

Gives explicit preconditions and alternatives: look the id up via get_categories, never guess, and confirm with the merchant before calling. It also names the two refusal cases (category with subcategories, integration-synced category) and what to do first, which is exactly the when-not guidance an agent needs.

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