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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. The description adds bulk support (recipient_ids) and notes action-specific parameter requirements, but does not explain other behavioral aspects like pagination details or error handling.

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?

Bullet list format is clear, but the listing of many actions is verbose and potentially redundant given the tool's focus on transfers. Could be more concise by omitting irrelevant actions.

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 ambiguity between multiple actions and the 'Flattened action: transfers' signal, the description fails to fully clarify the tool's scope. No output schema or return value description, leaving agents uncertain about results.

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?

Description adds meaning for some parameters (page, size for list; recipient_id for get; recipient_ids for bulk) but fails to explain 'data' and 'account'. With 0% schema coverage, the description partially compensates but is incomplete.

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?

Description lists multiple actions (list, get, default, balance, transfers, withdrawals, anticipations, anticipation_limits) but then states 'Flattened action: transfers', creating confusion about the tool's actual purpose. The name suggests transfers, but the description includes many non-transfer actions, making it ambiguous.

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. sibling tools like pagarme_recipients_list, pagarme_recipients_get, etc. The bulk support hint is present, but without context for selecting this tool over separate action-specific tools.

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