Criar ou substituir lote de cobranças Pix

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

Annotations already provide readOnlyHint (false), destructiveHint (false), and idempotentHint (true). The description adds that the operation 'altera o conteúdo integral do lote' (changes the entire content of the batch), providing context about full replacement. No contradiction with 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 is only two sentences, each providing essential information. It is front-loaded with the verb and resource, and there is no redundant or extraneous text.

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?

Given that an output schema exists, the description does not need to explain return values. It covers the purpose, usage, and behavioral trait of full batch replacement. Could mention authentication requirements, but that is typical and not mandatory.

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 100% with detailed descriptions for all parameters. The description adds a high-level summary ('várias cobranças coordenadas') but does not provide additional semantic value beyond what the schema already offers.

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 tool creates or replaces a batch of due Pix charges under an identifier. It specifies the verb (cria ou substitui), resource (lote de cobranças Pix com vencimento), and distinguishes from single-charge tools.

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 says 'Use para registrar várias cobranças coordenadas' (use to register multiple coordinated charges), indicating when to use it. However, it does not explicitly mention alternatives like pix_create_due_charge for single charges or pix_update_due_charge_batch for partial updates, which are siblings.

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