Criar Cartão de Crédito

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

The description adds that the operation is 'manual' and requires 'confirm=true', which is beyond the annotations. Annotations already indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description does not disclose other behavioral traits like response details or side effects, but the added requirement is valuable.

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 extremely concise—two short phrases. It front-loads the action and key requirement. Every word earns its place, with no filler.

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 9 parameters, 1 required, and the existence of an output schema (which reduces need to explain returns), the description is still far from complete. It lacks context on what 'manual' means, prerequisites, default behaviors, and how parameters interact. The output schema may help, but the description itself is insufficient.

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 only clarifies the 'confirm' parameter (requires true) but offers no additional meaning for the other 8 parameters (e.g., name, logo, account_id). This is insufficient for a complex creation tool.

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 it creates a credit card ('Cria cartão manual'). The verb 'Cria' and resource 'cartão' correctly identify the action and object. However, it lacks explicit differentiation from sibling tools like update or delete, though the context of 'create' is clear among credit card tools.

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 only one usage requirement ('Exige confirm=true') but no guidance on when to use this tool versus alternatives (e.g., list, update, delete). It doesn't mention prerequisites or context for manual creation vs. automatic processes.

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