delete_expense

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

The description adds 'irreversible' and 'confirm with user' beyond the destructiveHint annotation, providing clear behavioral context about permanence and user interaction.

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 very concise, with a single line and a warning emoji. It front-loads the key action and consequence, though it could include parameter details.

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 output schema exists, return values need not be explained. However, the single parameter lacks description, and the usage guidance is minimal. It is adequate for a simple delete but not fully 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 description coverage is 0%, and the description does not mention the expense_id parameter. The parameter name is self-explanatory, but the tool description should explicitly specify its role.

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 it deletes an expense and emphasizes irreversibility. However, it does not explicitly differentiate from sibling delete tools like delete_expense_attachment, though the resource name 'expense' is distinct.

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 instructs to confirm with the user, which is a usage guideline for destructive actions. It lacks details on when not to use or alternatives.

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