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

The description discloses that the tool creates a boleto and returns specific data, and mentions bulk behavior. It does not describe side effects, idempotency, or error conditions. With annotations having false values for all hints, the description carries moderate burden but covers only basic behavioral aspects, leaving some transparency gaps.

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 succinct and well-structured: two short paragraphs covering the core functionality, key constraints, and bulk support. Every sentence adds value, with no redundant or irrelevant content, making it highly concise and easy to parse.

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 tool's complexity (22 parameters, 11 required, no output schema), the description provides essential context: return values, minimum amount, address requirement, and bulk capability. However, it lacks explanations of parameter semantics, potential errors, or overall workflow, leaving gaps for agents needing full operational context. It covers the basics but not comprehensively.

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 description provides almost no parameter-level information. It only mentions that 'order_ids' is for bulk execution, but does not explain any of the 11 required parameters (e.g., payer_name, payer_cpf_cnpj, payer_street) or the meaning of optional ones. With 0% schema coverage, the description fails to compensate, leaving agents without clarity on parameter usage.

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 ('Emite um boleto bancário registrado') and the resource (boleto), and specifies the return values (linha digitável, código de barras, URL do PDF, transaction_id). It also distinguishes itself from the Pix tool by noting the required full payer address, making its purpose unambiguous.

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 when to use this tool (when issuing a boleto, not Pix) and provides key constraints: requires full payer address and a minimum value of R$ 3.00. It also mentions bulk support via order_ids, giving practical guidance. However, it does not explicitly compare with all sibling tools or state when NOT to use it beyond the Pix differentiation.

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