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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint, so the tool's safety profile is clear. The description adds useful details about pagination and filters, but includes contradictory action enumeration that may mislead about behavior.

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 front-loaded but includes extraneous action details that bloat it. The note about flattened action adds confusion. It could be much shorter and clearer by focusing solely on the list action and its parameters.

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?

With 6 parameters, no output schema, and no nested objects, the description should provide comprehensive usage context. It fails to explain the 'data' parameter format, the 'account' parameter, or any return structure, leaving significant gaps for an agent to invoke 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?

Schema description coverage is 0%, so the description must carry parameter info. It mentions page, size, data (filters), charge_id, and charge_ids, but does not explain the 'account' parameter or the format of 'data' (likely JSON). The explanation is incomplete for effective use.

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 lists multiple actions (list, summary, get, get_many) and notes 'Flattened action: list', creating ambiguity about whether this tool handles only list or multiple operations. This confuses the tool's specific purpose compared to sibling tools like pagarme_charges_get.

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 the many sibling charge tools (e.g., pagarme_charges_get, pagarme_charges_summary). The description implies multiple actions but does not explain selection criteria, leaving the agent without clear direction.

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