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

Annotations already declare destructiveHint=true, and readOnlyHint=false, establishing the operation as destructive. The description adds the important behavioral details that the deletion is permanent and requires explicit user confirmation, which goes beyond the annotation. There is no contradiction with the annotations.

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 consists of two tight sentences with no filler. The first sentence front-loads the core action and resource, and the second adds a critical safety prerequisite. 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?

For a straightforward delete operation with fully documented parameters and a destructiveHint annotation, the description is complete. It conveys the essential context: permanence, the need for explicit consent, and the target system. The absence of an output schema is acceptable because delete operations typically don't require return-value documentation.

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 fully documents all three parameters (id, company, confirm) with 100% coverage, so the baseline is 3. The description's mention of 'explicit user confirmation' mirrors the confirm parameter's schema description but adds no new parameter semantics. The description does not elaborate on id or company 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?

The description states a specific verb ('delete'), resource ('budget'), and system ('QuickBooks Online'), with the key qualifier 'permanently'. This clearly distinguishes it from sibling delete tools and from update_budget. The confirmation requirement adds further semantic precision.

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 provides a clear usage context: use when a budget must be permanently removed, and only after explicit user confirmation. It does not explicitly name alternatives like update_budget for non-destructive changes, but the confirmation prerequisite and the delete semantics make the intended use unambiguous.

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