create_scheduled_charge

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

No annotations provided, so description must cover behavioral traits. It explains mutation (schedules charge), silent charges for recurring, trialDays rebasing cycle, and recovery sweep. Lacks mention of webhook events or idempotency but is sufficient.

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?

Long but information-dense description. Front-loaded with purpose. Could benefit from bullet points or clearer separation of scenarios, but remains effective and avoids redundancy.

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?

With 12 parameters, complex logic (recurring vs one_time, multiple methods), and no output schema, description covers many nuances (trialDays, recovery, silent charges). Does not explicitly mention return value, but sufficiently complete for agent invocation.

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 coverage is 100% (baseline 3). Description adds value by linking methods to type (e.g., 'pix_automatic' is recurring-only), explaining trialDays behavior, and clarifying productId requirement. Goes beyond schema.

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?

Description explicitly states 'Schedule a future charge for an existing customer' with clear differentiation between one_time and recurring types, and references sibling tool list_customers.

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?

Provides guidance to use list_customers first, explains when each payment method (pix, boleto, card, pix_automatic) is appropriate, and clarifies constraints like 'Card method is recurring-only'. Does not explicitly enumerate when not to use but context is clear.

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