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

Annotations already declare destructiveHint=true, and the description reinforces with 'Irreversível'. It adds context about batch deletion (customer_ids, card_ids) and version V5. No contradictions with 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?

Two concise sentences: first defines core purpose and requirements, second adds bulk support. Front-loaded and efficient with no wasted words.

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 simple delete tool with clear annotations, the description covers essential aspects (purpose, parameters, irreversibility, bulk). No output schema exists, but return values are typically implied for deletes. Could mention success/error behavior, but adequate.

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 explains the required parameters (customer_id, card_id) and adds bulk parameters (card_ids, customer_ids). However, the 'account' parameter is left undocumented, leaving a minor gap.

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 the action ('Remove um cartão salvo'), the resource (card), the API version (Pagar.me V5), required parameters (customer_id + card_id), and irreversibility, distinguishing it from sibling tools like get, list, create, and renew.

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 specifies when to use the tool (to delete a card) and required parameters. It mentions bulk support, guiding users for batched execution. However, it lacks explicit alternatives or when-not conditions.

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