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

Annotations already declare destructiveHint=true, but the description adds the crucial context that deletion is permanent and requires explicit user confirmation. This goes beyond the annotation by informing the agent of irreversibility and the need for human consent, which is vital for a destructive operation.

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 a single sentence that conveys the core action, scope, and critical prerequisite (confirmation) with no unnecessary words. It is front-loaded with the verb and object.

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 delete operation, the description covers permanence and confirmation, and the schema covers all parameters. It does not mention cascading effects or prerequisites (e.g., whether the transaction must be voidable first), but given the annotations and simple parameter set, this is largely sufficient. The lack of an output schema is not an issue here.

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 schema already provides full descriptions for all three parameters (100% coverage), including the confirm flag's requirement to be true. The tool description reinforces the confirmation requirement but does not add new meaning beyond the schema. Baseline of 3 is appropriate given high schema coverage.

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 action (permanently delete) on a specific resource (credit card payment txn) within QuickBooks Online, which clearly distinguishes it from other delete tools for different entities. The addition of the confirmation requirement further clarifies the scope.

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 purpose is clear, and the resource type is unambiguous. However, it does not explicitly mention alternatives or exclusions, though the name and description make it evident this tool is for credit card payment transactions only. There is no need to list every other delete tool, but a note like 'for other transaction types, use the corresponding delete tool' would be explicit. It's adequate but not fully explicit.

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