delete_expense

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

The description discloses the destructive action ('Delete') and the return value on success. With no annotations, this is adequate for a simple delete operation, though failure behavior is not mentioned.

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: two sentences with no wasted words. The action is front-loaded, making it easy for an agent to quickly understand the tool's purpose.

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 one-parameter delete tool, the description covers the basic purpose and return value. However, it lacks details on error cases, idempotency, or any side effects, which would be valuable given no annotations or output schema details.

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 description only says 'by id,' which adds little beyond the parameter name 'expense_id' in the schema. With 0% schema description coverage, the description should provide more detail about the parameter.

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 an expense by id.' It uses a specific verb and resource, distinguishing it from sibling tools like create_expense, get_expense, list_expenses, and update_expense.

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?

Usage is implied: use when you want to delete an expense. However, there is no explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites or consequences.

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