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

The description fails to clarify behavioral traits beyond listing. Since readOnlyHint is false, the tool might mutate, but the description doesn't confirm that listing is safe. It includes a create action which implies mutation, but it's unclear if that action is actually available in this tool. The bulk support mention lacks details on limits or side effects.

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 poorly structured: actions are mixed, the 'Flattened action' note is confusing, and it includes irrelevant details (e.g., create action for a list tool). It is not concise and could be reduced to a clear statement about listing orders with parameter 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 6 parameters, no output schema, and 0% schema coverage, the description is severely lacking. It does not explain return format, pagination, filtering, or which parameters are required for listing. Sibling tools exist for get and create, but the description fails to clarify this tool's role, making it nearly unusable for an AI agent.

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 hints at usage for some parameters (order_id for get, reference_id for list), but leaves 'order' and 'account' unexplained. Given 0% schema description coverage, the description should compensate but only partially explains a few parameters. The bulk support mention for order_ids/reference_ids adds some context, but overall it's 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?

The tool name suggests listing orders, but the description includes actions for get and create, making the purpose ambiguous. The 'Flattened action: list' note adds confusion rather than clarity. It does not clearly distinguish this tool from sibling tools like pagseguro_orders_get and pagseguro_orders_create.

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 vs alternatives. It mentions that 'list' may require reference_id, but does not explain prerequisites, filtering options, or when to prefer this over pagseguro_orders_get for single orders. The inclusion of create/get actions further muddles usage.

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