delete_account_balance_history

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

Beyond the destructiveHint annotation, the description adds that the operation is 'irreversible' and 'affects the Net Worth views,' giving valuable behavioral context. There is no contradiction with annotations; in fact, it reinforces them.

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 two sentences, front-loaded with the action and scope ('Delete ALL historical balance entries'), and immediately points to an alternative. Every word earns its place.

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 simple delete operation, full schema coverage, and the destructiveHint annotation, the description covers scope, irreversibility, and impact on Net Worth. It does not mention the response format, but with no output schema and a straightforward mutation, this is a minor gap.

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 input schema provides full descriptions for both parameters with 100% coverage, so the baseline is 3. The description adds the phrase 'single account' but does not provide any new parameter-specific details beyond what the schema already offers.

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 ('Delete') with specific resource ('ALL historical balance entries') and scope ('for a single account'), and explicitly contrasts with the sibling tool by saying 'To remove a single month, use delete_balance_history_entry instead.' This distinguishes the tool from alternatives.

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 explicit when-to-use guidance by naming the alternative for partial deletion: 'To remove a single month, use delete_balance_history_entry instead.' Also notes the irreversible impact on Net Worth views, helping the agent decide when to invoke this tool.

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