Receipts Delete Receipt

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

Annotations already indicate destructiveHint=true. The description adds 'This may delete, clear, reset, or otherwise remove data,' which is redundant and vague—it does not clarify specifics like irreversibility, permission requirements, or side effects. The description adds minimal value beyond the 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 first sentence is concise and clear. The second sentence 'This may delete, clear, reset, or otherwise remove data' is redundant and adds unnecessary length without substance. Overall, it is short but could be improved by removing the filler.

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 destructive tool with 4 parameters and no output schema, the description is insufficient. It does not explain what happens after deletion (e.g., return value, confirmation), prerequisites, or constraints. Sibling tools exist (e.g., receipts_unmatch_receipt, receipts_update_receipt) but no guidance is provided for context.

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 50%, but the description does not explain any parameters. It omits details about 'receipt_id', 'fields', 'output_mode', and 'session_path', leaving the agent without guidance on how to use them. The description fails to compensate for the missing schema descriptions.

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 'Delete receipt,' which identifies the action and resource. However, it does not distinguish from sibling tools like 'delete_transaction' or 'delete_merchant,' and the additional vague sentence 'This may delete, clear, reset, or otherwise remove data' introduces ambiguity without improving clarity.

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 no context on when to use this tool versus alternatives, such as receipts_get_receipt or receipts_update_receipt. There are no explicit conditions, prerequisites, or exclusions to guide the agent.

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