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

Annotations indicate non-destructive and non-read-only, but the description does not disclose additional behavioral traits like authentication requirements or error handling. The 'só contas sk_' note adds some context but is incomplete.

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?

Moderately concise, but includes clutter like '[Flattened action: update]' and lacks a clear structure that separates action-specific guidance.

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 (5 parameters, no output schema), the description is incomplete: it does not explain return values, validation rules, or how bulk execution works in detail.

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 for data, order_id, closed, and order_ids, explaining their roles in different actions, but the account parameter is undefined, and with 0% schema description coverage, the explanation is insufficient.

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?

Description clearly states the tool creates/updates/closes orders in Pagar.me V5, but the '[Flattened action: update]' note is confusing and there is no differentiation from sibling tools pagarme_orders_write_create and pagarme_orders_write_close.

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?

Provides some guidance on using create, update, or close based on the operation, but lacks information on when to use this combined tool versus the separate sibling tools for create and close.

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