cancel_recurrence_scheduled_charge

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

Discloses key behaviors: in-flight cycle continues, series flips to recurrence_canceled after resolution, and tool is recurring-only. Without annotations, this provides valuable behavioral context beyond the schema.

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?

Three concise sentences, front-loaded with main action. No wasted words; every sentence adds value.

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?

Covers core behavior but lacks error conditions, prerequisites (e.g., charge must be recurring and not already canceled), and return value (no output schema). Adequate but not fully comprehensive.

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% with descriptions for both id and reason. Description adds no additional semantic detail beyond what the schema already provides, so baseline 3 is appropriate.

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 clearly states verb (stop future cycles) and resource (recurring scheduled charge). The phrase 'Final — use a new series to restart' and 'Recurring-only' distinguishes it from siblings like pause_scheduled_charge or set_cancel_at_period_end.

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?

Explains that in-flight cycle remains active until resolved, providing timing context. The 'Final' remark implies permanent cancellation, but does not explicitly compare to alternatives like pause_scheduled_charge or set_cancel_at_period_end.

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