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

Annotations are all false, so the description must carry the burden. It notes 'só sk_' (only secret key) indicating authentication requirement and mentions bulk support. However, it fails to disclose how actions are triggered, parameter dependencies for each action, error behavior, or idempotency. This is insufficient for safe invocation.

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 long and includes a repetitive list of actions with similar syntax. The note '[Flattened action: create]' is confusing and disrupts clarity. Could be streamlined to focus on the actual action mechanism.

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?

The tool claims multiple actions but provides no mechanism for action selection, leaving the agent guessing. No output schema, no details on return values or side effects. Given the complexity and low schema coverage, the description is critically incomplete.

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% (no description in schema). The description maps some actions to required parameters (e.g., update needs recipient_id+data) but leaves the 'account' parameter unexplained and does not specify how to select an action (e.g., via a parameter?). This partial mapping adds value but is incomplete and confusing.

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 (create, update, update_bank_account, create_withdrawal, create_anticipation) but includes the confusing note 'Flattened action: create', making it unclear which action the tool actually performs. The tool name suggests only create, yet the description implies a superset. This ambiguity differentiates poorly from sibling tools like pagarme_recipients_write_update.

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 versus the many sibling tools for specific operations (e.g., pagarme_recipients_write_update). The description does not clarify the intended scenario or provide any selection criteria, leaving the agent without direction.

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