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

Annotations include `destructiveHint: false` meaning it's not destructive, but the action is a cancellation which may have side effects. The description does not disclose what happens after cancellation (e.g., refund, notification), or whether it's reversible. Since annotations are neutral (no contradictions), the description adds minimal extra context, relying on the vague 'Cancela'.

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 two sentences long, concise, and front-loaded with the main purpose. Every sentence adds value: the first states the core action, the second mentions bulk support. No fluff 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?

The tool has 3 parameters, but the description only addresses two. No output schema exists, so the return value is not described. Annotations are sparse, and the description lacks details on prerequisites (e.g., charge must be unpaid) or error scenarios. Given its simplicity, it's minimally adequate but incomplete for full autonomous use.

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 coverage is 0%, so the description must compensate. It explains `transaction_id` as the identifier and introduces `transaction_ids` for bulk, but does not explain the `account` parameter at all. While it adds some value for two parameters, the `account` parameter remains undocumented, and no format or examples are given.

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 clearly states the action (cancel an unpaid Pix charge), specifies the resource (Pix charge), and includes the key identifier (`transaction_id`). It distinguishes itself from siblings like `paghiper_cancel_boleto` by targeting Pix specifically, though it doesn't name alternatives.

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 implies usage for canceling unpaid Pix charges and mentions bulk support via `transaction_ids`, but does not explicitly state when NOT to use it (e.g., for paid charges) or differentiate from `paghiper_cancel_boleto` beyond the resource type. No alternatives are named.

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