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

The description discloses that the tool works only with accounts having 'sk_' prefix, supports bulk execution via order_ids, and explains the three actions. However, it does not mention authentication requirements, rate limits, or side effects like whether creations are reversible. Annotations provide no additional safety hints, so the description carries the burden.

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 concise, front-loaded with the main purpose, and uses bullet points for actions. However, it mixes Portuguese and English and includes 'Flattened action: create' which adds minor confusion. No wasted sentences.

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 description covers the multi-action nature and bulk support well, but lacks explanation of the 'account' parameter and does not describe the return value (no output schema). Given the complexity, it is adequate but not fully complete.

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 description must explain parameters. It explains data (JSON for create/update), closed (for close action), order_id (required for update/close), and order_ids (for bulk). However, the 'account' parameter is not explained, leaving a gap. Overall, adds value but not complete.

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, updates, or closes orders (Criar/atualizar/fechar pedidos) and lists specific actions. However, the presence of sibling tools for update and close creates ambiguity about which tool to use, reducing clarity.

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?

No explicit guidance on when to use this tool versus sibling tools like pagarme_orders_write_update or pagarme_orders_write_close. The description mentions that update and close require order_id but does not advise the agent to use more specific tools when only a single action is needed.

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