POST /creditCard (Credit Card)

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

Annotations indicate a write operation that is not destructive. The description adds valuable behavioral context by stating that sensitive card data (number and CVC) are stored encrypted only in Cielo, which goes beyond the annotation hints.

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 a clear paragraph followed by a detailed example. It is front-loaded with the purpose and maintains efficiency, though the example could be slightly trimmed without losing meaning.

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?

The description covers purpose, input structure, and a security note, but lacks details on the output/response. For a write-intensive tool, knowing what is returned (e.g., the created card ID) would improve 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?

The input schema only defines a generic 'body' object with no internal properties, but the description provides an example with fields (customerId, number, name, etc.), effectively describing the parameters. Schema coverage is considered 100% due to the reference to the description.

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 tool registers a customer's credit card via Cielo, distinguishing it from other create tools like create_sale by focusing on card storage. The example further clarifies the resource.

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 provides no explicit guidance on when to use this tool versus alternatives such as create_charge or create_sale. It only notes a security detail without contextual usage advice.

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