delete_store

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

The description goes beyond the annotations (destructiveHint=true, idempotentHint=true) by explaining that deletion cascades to all products, variants, customers, carts, and orders, and that it cannot be undone. It also covers rate limits and dry-run adherence, adding valuable behavioral context.

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 well-structured with a one-line summary, followed by paragraphs for behavioral notes, authentication, and parameters. Every sentence adds value, and the format is concise and front-loaded.

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?

Given the tool's destructive nature and the presence of an output schema, the description covers all necessary aspects: purpose, side effects, usage precautions, authentication, rate limits, parameter details, and return value. Nothing important is omitted.

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 0% schema coverage, the description fully documents both parameters: store_id is described as the 'E-commerce store ID to delete,' and account is explained with an example and reference to list_accounts. This adds essential meaning beyond the schema's type-only definitions.

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 clearly states the tool's purpose: 'Permanently delete an e-commerce store from Mailchimp.' It specifies the exact resource and action, and distinguishes it from other delete tools by detailing the destructive cascade effect on associated data.

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: it warns about the destructive cascade and emphasizes careful verification of store_id. It also mentions authentication, rate limits, and dry-run modes, giving context for safe invocation.

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