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

Annotations correctly indicate readOnly, idempotent, and non-destructive behavior. The description adds 'Bulk support' which is a behavioral trait not in annotations. However, it doesn't mention error handling (e.g., if customer not found) or rate limits.

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 includes information about multiple actions, making it unfocused. It should be front-loaded with the specific purpose of this tool. The '[Flattened action: get]' note is helpful but buried.

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% parameter description coverage, the description is insufficient. It doesn't specify what the tool returns for a 'get' action (e.g., customer details). The bulk support mention is vague and doesn't explain batch execution behavior.

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%, so the description must explain parameters. It mentions customer_id, address_id, page, size, customer_ids, address_ids, but only in context of other actions. The 'data' and 'account' parameters are not explained. The mapping of parameters to the 'get' action is unclear.

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, list_addresses, get_address) and states 'Flattened action: get', but it's unclear what this specific tool does. The name implies retrieving a single customer, but the description mixes other actions, creating ambiguity.

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 sibling tools like pagarme_customers_list or pagarme_customers_get_address. The description implies that for 'get' you need customer_id, but it doesn't clearly differentiate usage scenarios.

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