Pay Bill

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation behavior is known. The description adds valuable context beyond that: it says the operation moves money, requires sufficient balance, may require pre-validation, and returns statuses. It skips details like failure/rollback behavior, but the category routing and prerequisites are transparent enough.

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 every section earns its placegiven the four category-specific argument shapes. It is well-organized: purpose, category routing, prerequisites, args per category, return shape, and examples. The heading/list structure makes it scannable despite its length.

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?

There is no output schema, so the inline return object is essential and present. It also covers prerequisites, optional behavior, category mapping, and natural-language examples. Nothing an agent needs to correctly select and invoke this tool seems missing.

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?

The input schema is empty, so the description carries the entire parameter burden. It defines category-specific parameters with names, types, and meanings, plus optional scheduling/saveBeneficiary fields. This is exactly the information an agent needs to construct a valid call.

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 uses specific verbs and resources: pays utility bills, buys airtime, purchases data bundles, and subscribes to cable TV. It clearly differentiates these from sibling tools by framing this as the bill-payment entry point with category-based routing.

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 pre-call steps: fetch biller codes, confirm NGN balance, and validate customer details for data and cable. It does not explicitly contrast with sibling money-transfer tools like monei_send_naira_to_bank, but the preconditions leave little doubt about when this tool should be used.

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