initiate_transfer

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

With no annotations provided, the description fully discloses key behaviors: moves real money (destructive), idempotent on merchantTxRef, amount in kobo. This is critical for agent safety.

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?

Four concise sentences, each adding distinct value. Front-loaded with purpose. No wasted words.

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 core behavioral aspects and key parameter semantics, but lacks information on return values, error handling, or prerequisites. For a real-money tool, minor gaps remain.

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?

Adds meaning for 'merchantTxRef' (idempotency key) and 'amountKobo' (unit), but 'bankCode', 'accountNumber', and 'narration' lack description. Schema coverage is low (20%), so more compensation needed.

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?

Clearly states the verb 'send a payout', the resource 'bank account', and critical constraints (real money, idempotency, kobo unit). Distinguishes from sibling tools like 'list_transfers' or 'create_virtual_account'.

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?

Implies use for sending payouts but lacks explicit when-to-use or when-not-to-use guidance relative to sibling tools. No mention of prerequisites or alternatives.

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