Delete price list

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds genuine business consequence – 'its prices stop applying immediately' – which is not derivable from structured fields and is the key risk an agent must convey to a user. It stops short of describing failure behavior on a missing/invalid ID.

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 short clauses, front-loaded with the verb and the consequence before the caution. No filler; the only soft cost is the all-caps emphasis, which is stylistic rather than wasted length.

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 the action, the immediate effect, and a confirmation requirement, while annotations cover reversibility and safety. Missing only edge-case behavior (what happens if the price_list_id does not exist).

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 0%, so the description carries the burden and mentions no parameter at all. The single parameter is a self-explanatory identifier (price_list_id), which limits the damage, but the description adds no semantics or format guidance beyond the name.

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?

Specific verb in caps plus exact resource: it deletes a price list. Among siblings like delete_product, delete_category, delete_collection and delete_variant, the resource noun alone pins down which entity is affected, so an agent can select it 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?

'Confirm with the user first' is a safety caution, not usage guidance. Nothing tells the agent when to prefer this over save_price_list, list_price_lists, or other deletion tools, nor what preconditions the target must satisfy.

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