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

The description discloses destructive behavior (delete_address) and batch execution, but annotations set destructiveHint=false, which contradicts the description. No info on authentication requirements (though 'só sk_' hints at API keys), rate limits, or idempotency is given. The contradiction lowers the score significantly.

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 organized with action bullet points and mentions bulk support, but the line '[Flattened action: update]' is confusing and adds little value. It could be more concise by removing that line and clarifying the action combination. Overall, it has a reasonable structure but some redundancy.

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 tool's complexity (six actions, bulk support) and lack of output schema, the description omits crucial details: expected return values, error handling, permissions, and detailed bulk usage. The 'data' field format is left ambiguous. Missing output schema makes it harder for the agent to use 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?

The description adds context to parameters, e.g., 'customer_id' is required for update and address actions, and 'data' includes fields like name, email. However, 'data' is typed as a string in the schema, but the description implies it should contain structured fields, which is vague. Schema description coverage is 0%, so the description provides some help 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?

The description clearly states it creates/updates customers and addresses in Pagar.me V5, listing five specific actions (create, update, create_address, update_address, delete_address). It distinguishes from sibling tools like pagarme_customers_write_create by being a combined write/update tool, but does not explicitly call out when to prefer more specific tools.

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 when-to-use or when-not-to-use guidance is provided. The description mentions bulk support and a 'flattened action: update' but does not advise on choosing between this tool and more specific siblings like pagarme_customers_write_create or pagarme_customers_write_update_address.

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