delete_store_customer

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

The description adds value beyond annotations by detailing the irreversible deletion, limited scope (store vs audience), authentication method, concurrency limit, and support for read-only/dry-run modes. Annotations already indicate destructive and idempotent but the description enriches understanding.

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 concise with a clear header, separate sections for args and returns, and no superfluous text. Every sentence provides essential information.

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?

The description covers the tool's purpose, effects, authentication, constraints, and response format. Despite complexity, the context is complete for an agent to invoke correctly.

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?

All three parameters are explained with basic meaning and the optional 'account' parameter is clarified with examples. Since input schema has 0% description coverage, the description compensates adequately.

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 'Permanently delete a customer from a store' with specific verb and resource. It distinguishes from sibling tools like 'delete_member_permanent' and 'delete_store_order' by targeting store customers.

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 explains the irreversible nature, what data is affected (store purchase data), and what is not affected (connected audience). It also provides authentication and rate limit context. However, it does not explicitly list alternative tools for similar operations.

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