delete_store_customer

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

Annotations already set destructiveHint=true and idempotentHint=true, and the description adds valuable context: what exactly is deleted (link to store purchase data) and what is not (connected audience), plus the permanence. No contradiction with annotations.

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 (6 sentences) with a clear structure: purpose, caveats, parameter list, return format. No fluff, each sentence serves a purpose.

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 delete tool with low complexity, the description covers key points: action, scope, return format. However, it lacks details on optional parameter (account) and error conditions. Output schema exists but is not fully described. Adequate but with minor gaps.

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 must compensate. It only briefly explains the required parameters (store_id, customer_id) and omits the optional 'account' parameter entirely. Minimal guidance beyond names, lacking format, source, or validation hints.

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 'permanently delete a customer from a store' and distinguishes from siblings like delete_member (audience) and delete_store. It also clarifies what it does not affect (connected audience), making the purpose unambiguous.

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 indicates when to use (to remove a customer from store data) and notes it cannot be undone, but does not explicitly exclude use cases or mention prerequisites like permissions. The distinction from sibling tools is implied, making it fairly clear.

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