create_virtual_account

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

With no annotations provided, the description carries the full burden. It discloses that money is in integer kobo (1 Naira = 100 kobo) and that test-mode keys create sandbox accounts. However, it does not mention authorization requirements, side effects, or whether the operation is reversible.

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 sentences, front-loading the main purpose. Every word serves a purpose: creation, test-mode distinction, and unit clarification. No unnecessary details.

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 no output schema, the description omits what the tool returns (e.g., account number, status). It covers test-mode behavior and unit convention, but lacks guidance on reconciliation or next steps. For a tool with 5 parameters, it is moderately complete but could be richer.

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 60%, so the description adds moderate value. It clarifies that 'expectedAmountKobo' is in integer kobo, which is already in the schema. Other parameters like name, email, phone, and accountRef are not elaborated beyond schema descriptions. The test-mode context is implicit, not parameter-specific.

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 'Provision a dedicated virtual account (NUBAN) for a customer,' using a specific verb and resource. It distinguishes from sibling tools like delete_virtual_account and get_virtual_account by implying creation. The mention of test-mode behavior adds clarity.

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 gives no explicit guidance on when to use this tool versus alternatives like list_virtual_accounts or simulate_deposit. It only mentions test-mode behavior, but does not specify use cases or preconditions. The agent must infer usage from the name.

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