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

The description states the tool performs a read operation ('get' returns details), but annotations set readOnlyHint to false, indicating possible mutations. This contradiction undermines trust. No side effects or behavioral traits beyond the immediate action are disclosed.

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 cluttered with details about cancel and refund actions that belong to other tools. The 'Flattened action: get' statement is helpful but the bulk of the text is extraneous.

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 no output schema and 0% property descriptions, the description must provide comprehensive guidance. It fails to explain key parameters (account, amount_cents) and the response format, leaving the agent underinformed.

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 input schema has zero description coverage (0%). The description explains charge_id for get and mentions charge_ids for bulk, but fails to account for account and amount_cents parameters. The bulk support description conflicts with the 'single charge' claim, causing confusion.

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 retrieves details of a single charge via 'get' action with a required charge_id. However, it includes unrelated actions (cancel, refund) which could confuse an agent, slightly reducing clarity.

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 is given on when to use this tool versus sibling tools like pagseguro_charges_cancel or pagseguro_charges_refund. The description only lists actions without context for selection.

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