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

Annotations only establish that this is a non-read-only, non-idempotent, open-world write. The description adds far more: no charge occurs at creation time, funds move only when the schedule fires, payment depends on a funded on-chain allowance then, PIN is always required, and the outcome is either auto-pay or notify-only. This is exactly the mutation-side context annotations cannot convey.

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 purpose is front-loaded in the first clause, followed by prerequisites, side-effect timing, and the fallback path, in that order. Despite its length every sentence carries distinct operational information; there is 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?

For a 15-parameter write tool with no output schema, the description covers the workflow end to end: validation model, required credentials, when money actually moves, the two possible schedule modes, and even what the response reports. An agent has enough to call it correctly and interpret the result.

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%, so the schema already documents each field; the baseline is 3. The description nevertheless adds cross-parameter reasoning — the pay_bill validation model, the list_plans dependency for variation_code, the mandatory PIN — and explains that customer_email exists because the channel cannot push notifications back. Some of this restates the schema, but the interaction guidance is genuine added meaning.

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 opening sentence states a specific verb (set up) plus resource (recurring/future one-off bill payment) and enumerates the covered service types. It immediately distinguishes itself from the sibling pay_bill by scope — this creates a standing schedule rather than paying now.

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?

It gives explicit prerequisites (call list_plans first for DATA/CABLE variation codes), explicit exclusions (EDUCATION and INTERNATIONAL cannot be scheduled — use pay_bill), and explicit sibling routing (list_schedules to view, cancel_schedule to remove). Nothing about when to choose this tool is left to inference.

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