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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not burdened by stating basic safety. It adds valuable behavioral context by emphasizing permanence and requiring explicit user confirmation, which are important for an irreversible mutation.

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, direct sentences with no filler. The key information (permanence and confirmation requirement) is front-loaded and every clause 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 simple destructive operation with full schema coverage and strong annotations, the description captures the essential prerequisites (permanence, user confirmation). It does not describe success/error outcomes, but no output schema exists and the operation's core behavior is sufficiently communicated.

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 the schema fully documents id, company, and confirm. The description's mention of 'explicit user confirmation' reinforces the confirm parameter's requirement, but it does not add new parameter-level meaning beyond what the schema already provides.

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 uses a specific verb ('delete') and resource ('recurring transaction from QuickBooks Online'), clearly distinguishing it from the many sibling delete_* tools. Adding 'Permanently' clarifies the operation's scope and irreversibility.

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 clearly states the operation targets a recurring transaction and that explicit user confirmation is required before deletion. However, it does not explicitly mention alternatives (e.g., deactivating rather than deleting, or using search/get tools first) or give when-to-use versus when-not-to-use guidance among the sibling tools.

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