Delete Product from Import List

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

While annotations already indicate destructiveHint=true, the description adds substantial behavioral context beyond annotations: the irreversible nature ('IRREVERSIBLE — the product cannot be recovered'), the two-step confirmation flow, business consequences ('losing the supplier mapping'), and detailed agent protocol requirements. This significantly enhances understanding of the tool's behavior.

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 description is appropriately sized and front-loaded with critical information (irreversible nature, confirmation requirement). While comprehensive, every sentence adds value - no redundant information. The structure moves from core functionality to business context to agent protocol in a logical flow.

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 tool with no output schema, the description provides complete context: clear purpose, usage guidelines, behavioral transparency (including irreversible consequences), parameter semantics, business implications, and detailed agent protocol. It addresses all aspects needed for safe and correct tool invocation.

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?

With 100% schema description coverage, the baseline is 3. The description adds meaningful context about the confirm parameter's purpose in the deletion flow ('If called without confirm=true, returns a confirmation prompt — show this to the user') and the import_item_id's business significance ('losing the supplier mapping'), providing semantic understanding beyond the schema's technical documentation.

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?

The description explicitly states 'Permanently delete a product from the DSers import list' - a specific verb ('delete') and resource ('product from DSers import list'). It clearly distinguishes from siblings by specifying this only affects the import list, not store listings, and mentions alternatives like using Shopify/Wix admin directly for store products.

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 provides explicit guidance on when to use this tool vs alternatives: 'Only removes the product from DSers import list (pre-push staging area). Products already pushed to Shopify/Wix stores are NOT affected — to remove a store listing, use the Shopify/Wix admin directly.' It also specifies prerequisites (user confirmation) and the multi-step protocol for proper usage.

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