Pay Bill

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

With no annotations, the description carries the burden of behavior disclosure. It does state key traits: immediate execution, on-chain settlement, and funding from the linked wallet. Yet it omits important details such as irreversibility, failure modes, confirmation behavior, or the requirement of a PIN, which is a required schema parameter.

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 two tight sentences that front-load the core purpose and scope, followed by the behavioral constraint. No filler, repetition of the title, or extraneous detail.

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—14 parameters, 4 enums, no annotations, and no output schema—this two-sentence description is far from sufficient. It does not explain how to construct a valid request for different bill types, which parameters are conditional, or what the response/outcome looks like.

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 only 7%, so the description must compensate. It offers some genre-level context (Nigerian vs international, airtime/data/etc., on-chain settlement) but leaves most parameters—api_key, provider, meter_type, operator_id, variation_code, product_type_id, customer_email, amount_ngn—entirely unexplained.

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 identifies the operation: paying a real bill from a linked wallet, settled on-chain. It scopes the supported categories (Nigerian airtime/data/electricity/cable/education, international airtime/data) and notes immediate execution, which differentiates it from scheduling tools.

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 conveys that this tool executes immediately and notes 'no delay parameter exists', effectively signaling it is for instant payments. However, it does not explicitly name alternative tools like schedule_bill or pay_bill_batch, nor does it provide explicit when-not-to-use conditions.

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