Delete Budget Line Item

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

Annotations already indicate destructiveHint=true and idempotentHint=true. Description adds emphasis on permanence ('This cannot be undone') and lists required parameters. Does not contradict annotations and adds value by clarifying the irreversible nature.

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?

Description contains redundant statements ('This cannot be undone' repeated twice). Could be more concise by removing duplication. Front-loads action but includes extra API reference that may be unnecessary for selection.

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 simple delete tool with three required parameters and no output schema, the description covers purpose, permanence, required fields, and API endpoint. Lacks error handling info (e.g., behavior on non-existent item) but is adequate.

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?

Input schema covers all three parameters with descriptions (100% coverage). Description merely restates the required parameters without adding further meaning or constraints beyond the schema.

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?

Clearly states 'Deletes a specified budget line item' with a specific verb and resource. Distinguishes from siblings like update_budget_line_item or show_budget_line_item by emphasizing permanent removal.

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?

Provides some guidance ('Use this to permanently delete') and lists required parameters, but does not explicitly exclude use cases or mention alternatives (e.g., deactivation, soft delete). Context is implicit for a delete operation.

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