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

Annotations declare readOnlyHint=true and idempotentHint=true, which are consistent with the listed actions (all read operations). However, the description is confusing by offering multiple actions without clarifying how the agent controls which action executes. The bulk support mention adds some value, but overall the behavioral model is unclear.

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 verbose and redundant, listing all actions then stating 'Flattened action: get'. It includes extraneous information (Portuguese text for the API version) that does not help the agent. A more focused description would be more effective.

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 with 0% schema coverage, no output schema, and many sibling tools, the description is severely incomplete. It fails to explain how actions are selected, what each action returns, or when to use bulk mode. The agent cannot reliably invoke this tool without additional context.

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 coverage is 0%, and the description only implicitly mentions some parameters (page, size, recipient_id, recipient_ids) but does not explain the 'data' or 'account' parameters. It also does not describe how to specify the desired action (e.g., via a parameter). This leaves the agent uncertain about how to invoke the correct operation.

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, get, default, balance, transfers, etc.) but then says '[Flattened action: get]' and includes bulk support. It does not clearly state the tool's primary purpose as a single get operation; instead it appears to be a multi-action router, which conflicts with the tool name 'pagarme_recipients_get'. This confuses the agent about what the tool actually does.

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 tools that cover specific actions (e.g., pagarme_recipients_list, pagarme_recipients_balance). The description lacks any context about when to prefer this aggregated tool over the more specialized ones.

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