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

The description claims 'get' (read) but annotations set readOnlyHint=false, indicating possible mutation. This is a contradiction. Additionally, no details on side effects, permissions, or behavior for bulk requests.

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 rambling, mixing unrelated actions and including irrelevant details like 'list' and 'create'. The flattened action note adds confusion rather than clarity.

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 no annotation hints, the description lacks essential details like return format, error handling, and prerequisites. It is insufficient for an agent to use the tool correctly.

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?

Adds meaning for order_id (single get) and order_ids/reference_ids (bulk), but fails to explain account, reference_id, or the 'order' object. With 0% schema coverage, the description compensates only partially.

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 mixes actions list, get, and create, then says 'Flattened action: get'. It is unclear whether the tool is solely a get operation or supports multiple actions. The name 'pagseguro_orders_get' suggests get, but the description muddles the purpose.

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 guidance on when to use this tool versus siblings like pagseguro_orders_list or pagseguro_orders_create. The description even mentions list and create actions, which are separate tools, potentially misleading the agent.

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