delete_expense

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

Discloses key behavior: record stays in database with is_deleted=1, which is critical for a deletion tool. No annotations exist, so description carries full burden. No contradictions.

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?

Extremely concise with two sentences. Front-loaded with the action and core distinction (soft-delete and restoration). No wasted words.

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?

Covers the main behavior and output schema presumably exists. But missing parameter description leaves a gap for a simple tool. Adequate but not thorough.

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 coverage is 0%, and the description does not mention the 'expense_id' parameter or its role, despite it being self-explanatory. Description adds no value for parameter usage.

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 action 'Soft-delete' on the resource 'expense' and distinguishes from the sibling 'restore_expense' by mentioning it can be restored.

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 states the tool is for soft-deletion and points to 'restore_expense' for recovery, giving clear context. However, it lacks explicit when-not-to-use guidance for sibling tools like 'delete_category'.

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