Criar cobrança por cartão

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

Annotations already indicate write, non-idempotent, and destructive behavior. The description adds that it 'submits' the charge, implying an action that will charge the customer, but does not disclose additional traits like side effects, error conditions, or idempotency specifics beyond what annotations provide.

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 single, efficient sentence that fronts the purpose. It is concise, though could be slightly more structured for readability.

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 (nested objects, many siblings), the description is brief. It relies on annotations and output schema for completeness, but could better address when to choose this over similar tools like create_one_step_charge.

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 100%, so the schema already documents each parameter. The description adds no specific parameter meaning beyond the overall context, meeting the baseline for high coverage.

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 creates and submits a credit card charge. It specifies the resource and action, but does not explicitly distinguish from sibling tools like create_one_step_charge or create_charge, leaving some ambiguity about when to use this specific route.

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 advises use when a payment token and required data are available, providing a usage condition. However, it lacks explicit exclusions, alternatives, or when-not-to-use guidance, limiting its help for an agent comparing multiple charge tools.

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