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

Annotations already indicate read-only, idempotent, not destructive. The description adds that the tool supports batched execution via customer_ids and card_ids, which is useful. However, it does not explain behavior when both customer_id and card_id are provided, nor does it mention pagination or error handling.

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 relatively short and structured: resource, actions, bulk support. However, the redundancy of listing both 'list' and 'get' actions and then noting 'Flattened action: list' could be streamlined. Still, it is not overly verbose.

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?

For a list tool with 5 parameters and no output schema, the description lacks critical details such as the format of the returned cards, pagination, maximum batch size, or error scenarios. While it mentions bulk support, it is insufficient for complete agent understanding.

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 description coverage is 0%, so the description must clarify parameters. It partially explains customer_id (required) and mentions bulk support for customer_ids and card_ids. However, the account parameter is not described, and the role of card_id is unclear (used for get but flattened to list). No description of the remaining parameters.

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 identifies the tool as listing saved cards of a customer in Pagar.me V5. It mentions list and get actions but notes 'Flattened action: list', which is somewhat confusing. It distinguishes from siblings like pagarme_cards_delete and pagarme_cards_get, but the role of the 'get' action in a list tool adds 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 states that list and get require customer_id and mentions bulk support, but it does not clarify when to use this tool versus pagarme_cards_get for single card retrieval. No explicit guidance on when not to use the tool or alternatives.

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