aza_buy_airtime

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

With no annotations, the description carries full burden, and it explains the core behavior (buy airtime, paid from wallet). However, it does not disclose other behavioral aspects such as whether the operation is reversible, any rate limits, or confirmation steps. For a simple purchase, this is adequate but not thorough.

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 extremely concise: two sentences with no redundant words. It front-loads the action and key context (target, payment, currency). Every sentence serves a purpose.

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 simplicity of the tool (3 straightforward parameters, no output schema), the description covers all essential context: what it does, how payment works, and target audience. It does not discuss edge cases or error conditions, but that is acceptable for this level of complexity.

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 100%, so the schema already documents all parameters. The description adds marginal value beyond schema, such as clarifying that amount is in naira (already in schema). There is no additional semantic enrichment for parameters.

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 states the action (buy), resource (airtime), target (Nigerian phone number), payment method (connected Aza wallet), and currency (naira). It effectively distinguishes from sibling tool aza_buy_data which buys data bundles.

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 provides context by mentioning the payment source (Aza wallet) and currency (naira). It implicitly differentiates from siblings by domain (airtime vs data), but lacks explicit instructions on when to use or not use, and does not mention prerequisites like wallet connection.

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