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

Annotations are present but minimal (readOnlyHint=false, destructiveHint=false). The description does not disclose side effects, idempotency, or error conditions beyond the account restriction and action summaries.

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 moderately concise with bullet points and a note about flattened action. It conveys essential information without excessive verbosity.

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 (multiple actions, bulk support) and lack of output schema, the description provides adequate information for the primary close operation but may not fully cover create/update usage or error handling.

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 adds meaning to parameters: 'data' is JSON for create/update, 'closed' boolean for close, 'account' restricted to sk_, 'order_id' required for update/close, 'order_ids' for bulk. This compensates for the 0% schema coverage.

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 can create, update, or close orders in Pagar.me V5. The naming and 'Flattened action: close' indicate the primary purpose is closing/reopening, but the inclusion of create and update actions adds some ambiguity.

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 mentions a restriction to 'sk_' accounts and lists actions with their requirements, but does not provide explicit guidance on when to use this tool versus specialized siblings like pagarme_orders_write_create or pagarme_orders_write_update.

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