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

Annotations readOnlyHint=true, idempotentHint=true, destructiveHint=false already indicate a safe read operation. The description adds that get_many returns { results, errors }, providing behavioral context. However, it does not fully disclose behavior for all parameters (e.g., what happens without order_id).

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 somewhat verbose, listing all actions before flattening. It could be more direct about the get action. It is not poorly structured but contains extra information that may distract.

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 has 6 parameters with no descriptions and no output schema, the description provides insufficient context. It omits details on output format (except for get_many), account handling, and the role of data/account parameters.

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?

With 0% schema description coverage, the description must compensate. It explains order_id and order_ids, but ignores data, page, size, and account. Only 2 of 6 parameters are described, leaving significant gaps.

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 that the tool is for retrieving order details (get and get_many) from Pagar.me V5, with specific mention of 'get: detalhe por order_id' and 'get_many: busca vários por order_ids'. However, it also includes list action, which may cause confusion since sibling tool pagarme_orders_list exists.

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 does not provide guidance on when to use this tool versus alternatives like pagarme_orders_list or pagarme_orders_get_many. It lists multiple actions but declares '[Flattened action: get]', lacking explicit when-to-use and when-not-to-use instructions.

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