Criar cobrança Pix com vencimento

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

Annotations already indicate that this tool is not read-only (readOnlyHint=false), is state-changing (openWorldHint=true), idempotent (idempotentHint=true), and not destructive (destructiveHint=false). The description adds that the txid is defined by the receiver, which is a useful behavioral detail beyond annotations. However, it does not disclose other side effects or prerequisites.

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, well-formed sentence with no redundant words. It front-loads the primary action and then provides a clear usage condition.

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 the complexity of the input (nested objects) and the presence of an output schema, the description provides sufficient high-level context for selecting the tool. It could benefit from summarizing the required nested structures, but the schema already details those.

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 baseline is 3. The description adds value by clarifying that the txid is defined by the receiver and that the tool involves 'data de vencimento e das regras financeiras,' which maps to calendario and valor fields, providing context beyond the schema.

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 verb 'Cria' (creates), the resource 'cobrança Pix com vencimento' (Pix charge with due date), and specifies the use of a txid defined by the receiver. This distinguishes it from sibling tools like pix_create_immediate_charge, which lack due date constraints.

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 provides explicit guidance on when to use this tool: 'Use quando a cobrança precisar de data de vencimento e das regras financeiras admitidas para cobranças desse tipo.' It does not explicitly mention alternatives or when not to use, but the context of sibling tools implies them.

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