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

Annotations provide readOnlyHint, idempotentHint, and destructiveHint, indicating a safe operation. The description adds useful behavioral context like bulk support via customer_ids and address_ids, and pagination with page/size. It does not contradict annotations.

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 somewhat verbose with multiple actions and a flattened action note, but it is structured with bullet points. It could be more concise by focusing solely on the list action.

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 (8 optional parameters, no output schema), the description lacks complete guidance. It does not describe the return format, the exact meaning of 'data' parameter, or how bulk execution works in detail. Annotations cover safety but not functional completeness.

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?

With 0% schema description coverage, the description must compensate. It explains parameters for the list action (page, size, data) and mentions customer_id, address_id, customer_ids, address_ids in context. However, the 'account' parameter is not explained, and the 'data' parameter's exact role is ambiguous (filter vs. output fields).

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 indicates the tool is for listing customers, with the action 'list' highlighted via 'Flattened action: list'. It includes specific fields (name, email, document, code) and differentiates from sibling tools like pagarme_customers_get and pagarme_customers_list_addresses. However, the inclusion of multiple actions (get, list_addresses, get_address) adds slight 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?

The description implies usage for listing customers but does not explicitly state when to use this tool versus alternatives. It mentions the list action with parameters, but no explicit when-not or alternative tool guidance.

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