billing_history_delete

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description merely restates 'Delete' without adding anything beyond that. It does not say whether the deletion is permanent/irreversible, what the uuid identifies, or what protections or permissions apply.

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?

Four words, front-loaded with the verb, so there is no padding to trim. But the terseness is under-specification rather than efficiency for a destructive one-parameter tool.

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 destructive tool with no output schema and an undocumented parameter, the description leaves key facts unstated: permanence of deletion, what the uuid selects, and any prerequisite step. An agent could call it, but not confidently.

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 description coverage is 0% for the single uuid parameter, and the description does not compensate by explaining what the uuid refers to (a billing history entry). The bare 'infra billing history' phrase gives no mapping between the parameter and the record to delete.

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?

States a specific verb ('Delete') and resource ('infra billing history'), which distinguishes it from the sibling billing_history_create and billing_history_list. It does not, however, say what a single deletion targets (a record identified by uuid) or add any differentiation beyond what the name already conveys.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The destructive nature is never acknowledged, and there is no hint about confirming intent or using billing_history_list first to find the target record.

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