Receipts: delete receipt by id_by_customer

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

Annotations already declare destructiveHint=true, but the description adds valuable context: it warns of destructiveness, requires user confirmation, and notes that receipt deletes are restorable while cost-location deletes are not. This goes beyond 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, including a warning emoji, a one-sentence summary, and a note on prerequisite. It could be slightly tighter but is mostly efficient.

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 purpose, prerequisite, and destructive behavior, but lacks details on the missing id_by_customer parameter and what happens on success (no output schema). The missing param reduces completeness for a simple tool.

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?

The input schema only lists api_key, but the description implies an id_by_customer parameter, which is not present. This mismatch confuses parameter semantics despite 100% schema coverage for the listed param. The description does not clarify how id_by_customer is provided.

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 deletes a receipt by id_by_customer for a specified customer account. The verb 'delete' and resource 'receipt' are specific, and it distinguishes from sibling restore tools.

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 advises to get the id_by_customer via '/receipts/get method' first, providing a clear prerequisite. However, it does not explicitly compare with other delete tools or state when not to use.

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