delete_store_cart

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

No annotations provided, so description carries full burden. Discloses irreversibility (cannot be undone), authentication (API key), rate limit (max 10 concurrent), respect for read-only/dry-run modes, and error return (404). Covers key behavioral traits.

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?

Approximately 100 words with a clear structure: purpose, usage, behavior, arguments, returns. No redundant information. Front-loaded with essential information. Efficient and well-organized.

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 simplicity (2 params, straightforward delete), the description covers purpose, usage, behavior, params, and return format. No annotations but description fills the gap well. Minor omission: no mention of other error conditions beyond 404, but overall complete.

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 provides parameter names but no descriptions (coverage 0%). Description adds minimal one-line descriptions ('E-commerce store ID', 'Cart ID to delete'), which are adequate but lack format constraints or examples. Sufficient for basic understanding.

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 cart from a store' with specific verb and resource, and differentiates from siblings by focusing on store carts, which is distinct from other delete operations in the tool set.

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?

Explicitly says when to use: 'when an external system reports the cart has been completed or expired.' Also clarifies what it does not affect (orders, customer records), guiding appropriate use. Lacks explicit when-not-to-use but is strong overall.

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