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

Annotations already mark destructiveHint=true, and the description adds value by stating the deletion is permanent and that explicit user confirmation is required. This extra context reinforces the confirm parameter's role and warns the agent that the action is irreversible, which is important behavioral guidance beyond the annotation alone.

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?

Two short sentences, both informative and front-loaded. The first names the operation and its scope; the second provides the critical safety condition. There is no filler or repetition.

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 single-entity delete tool with 100% schema coverage, destructive annotation, and no nested objects, the description covers the essential operational and safety context. It could add detail about what the response contains or how to confirm success, but the tool is simple enough that this is not a critical 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?

Schema description coverage is 100%, so all three parameters (id, company, confirm) are already documented in the schema. The description's statement that the action 'Requires explicit user confirmation' aligns with the confirm parameter but adds little new semantic meaning beyond what the schema already states.

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'), a specific resource ('inventory adjustment'), and the target system ('QuickBooks Online'), and makes the destructive nature explicit with 'Permanently'. This clearly distinguishes it from the many sibling delete_* tools, which act on different resources.

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?

Usage is implied: use this tool when the user wants to delete an inventory adjustment. However, the description does not explicitly say when not to use it or mention any alternative such as void_inventory_adjustment or get_inventory_adjustment for verification. The confirmation requirement hints at the decision gate but does not provide deeper routing guidance.

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