Delete variant category

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the authorization scope (edit_products) and a mandatory per-call confirmation gate, which an agent needs in order to invoke correctly.

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 tight sentences, front-loaded with the action, then endpoint, scope and confirmation requirement. No filler, though the 'Reviewed native ...' phrasing is slightly telegraphic rather than purely functional.

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 destructive, non-idempotent mutation with no output schema, the description supplies the endpoint, required scope and the confirmation gate, and annotations supply the destructive/idempotency profile. It is essentially complete, missing only an explicit statement of irreversibility or error behavior, which is minor.

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 baseline is 3, and the description adds meaning beyond it by explaining that 'confirm' is a per-call explicit confirmation gate rather than an ordinary boolean, matching the schema's 'Set true only when the user asked for exactly this action'. It does not add anything for product_id/variant_category_id, but the schema already documents those opaque IDs.

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+resource (delete a variant category) and pins it to the native endpoint DELETE /products/:product_id/variant_categories/:id, which clearly separates it from delete_variant, delete_product and the other delete_* siblings. An agent can identify the target entity without opening the schema.

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?

Adds a real prerequisite — 'Requires explicit per-call confirmation' — and names the required scope (edit_products). However it never states when to choose this over alternatives (e.g. update_variant_category, disable/delete at a different level), so usage is implied rather than guided.

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