delete_expense

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

Annotations already declare destructiveHint=true and readOnlyHint=false, indicating a destructive write operation. The description adds no further behavioral context beyond restating the action; it does not mention side effects, irreversibility, or the nature of the response. It does not contradict the annotations, so it meets the baseline but adds little value.

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 a single, concise sentence that clearly communicates the action and target. It is front-loaded and contains no extraneous words, achieving appropriate brevity for a simple operation.

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 single-parameter delete operation with no output schema, the description covers the essential purpose and key parameter. It does not describe return values or error conditions, but these are often standard for delete operations and are not critical given the tool's simplicity. The description is complete enough for an agent to call it correctly.

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 schema fully covers the single parameter 'id' with a description, and the tool description also mentions 'by ID', but adds no additional semantic detail beyond what the schema provides. With 100% schema description coverage, the baseline of 3 applies.

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 'delete an existing expense by ID' clearly states the action (delete) and the resource (expense), and specifies the identifier used. It is unambiguous and easily distinguishes from siblings like add_expense, update_expense, and list_expenses through the verb and resource.

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 implicitly conveys usage by the verb 'delete', but it does not explicitly state when to use it versus the alternatives, nor does it mention any constraints such as required existence or irreversibility. The context is clear enough for an agent to infer usage, but no explicit guidance or exclusions are provided.

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