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

Annotations declare destructive/openWorld/non-idempotent, and the description goes further: it discloses that money moves irreversibly and immediately, that PIN is always required even under OAuth, that api_key is only needed without OAuth, and that no queue/schedule parameter exists. That is material context beyond the annotations.

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?

Front-loaded with the core action and the anti-scheduling warning, and every paragraph carries safety-relevant content. It is long and repeats the PIN requirement and the 'never guess' instruction, but for a destructive, irreversible payment tool the redundancy is defensible rather than wasteful.

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 the full decision surface for a 15-parameter destructive tool: per-service required fields, prerequisite lookups, auth modes, confirmation requirement, and the scheduling exception. No output schema exists, but the description does not need to explain return values for an agent to call it correctly.

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 baseline is 3. The description adds cross-parameter workflow constraints the schema cannot express on its own — which fields are mandatory per service and that country/product_type_id/operator_id/variation_code must be copied verbatim from list_international_options and never guessed. It is largely corroborative of schema text, so it lands above baseline but not at 5.

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?

States a concrete verb+resource and enumerates the bill categories covered (airtime, data, electricity, cable, education, international), plus the settlement path (linked wallet, on-chain). It is clearly distinguishable from siblings like schedule_bill and pay_bill_batch, especially given the explicit 'EXECUTES IMMEDIATELY, no scheduling' clause.

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?

Explicit routing to alternatives and prerequisites: call list_plans first for DATA/CABLE/EDUCATION, list_international_options for INTERNATIONAL, and it names the delay path (AbaPay app / Telegram/WhatsApp/X) as the alternative to this call. It also states the human-confirmation precondition before invoking.

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