initiate_transfer

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. While 'instantly' hints at speed, it does not disclose whether the operation is idempotent, what happens to the sender's balance, what errors can occur, or if there are fees. The description's claim of 'instant' is vague and lacks detail about actual behavior.

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 a single sentence of 10 words, which is concise and front-loaded. However, it sacrifices necessary detail for brevity, leaving out critical context. Conciseness is achieved but at the cost of completeness, making it merely adequate.

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?

The tool has 9 parameters (6 required), nested objects (headers), and no output schema. The description covers only the high-level purpose. It omits how to specify the channel number, how headers are passed, what the externalref format should be, whether the transfer is immediate or might be delayed, and what the response looks like. Given the complexity, the description is insufficiently complete.

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 coverage is 100%, so all 9 parameters have descriptions in the schema. The description does not add any information beyond what is already in the schema (e.g., it does not clarify the channel mapping or required credentials). Baseline 3 is appropriate as the description adds no marginal value for parameter understanding.

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 ('Send money') and the target resource ('Mobile Money or Bank Account'), with the adverb 'instantly' adding temporal specificity. This is sufficient to distinguish from many sibling tools like 'internal_transfer' or 'send_sms', though it does not explicitly differentiate from 'initiate_payment' or 'transfer_status'.

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 no guidance on when to use this tool versus alternatives such as 'internal_transfer' (internal account transfers) or 'initiate_payment' (possibly different payment flows). No when-not-to-use conditions or context triggers are mentioned, leaving the agent without decision support.

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