Create payout

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description reinforces this and adds useful context: 'Highest-risk destructive write' and 'send money outward' clarify the real-world consequence. It also warns to verify key parameters, which is valuable behavioral guidance beyond the boolean hints.

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, dense sentence that front-loads the most critical warning and immediately states the action. Every word contributes to the message, with zero filler or redundancy.

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?

For a high-risk mutation tool with 9 parameters, no output schema, and no enum/schema guidance, a one-sentence warning is not enough. The agent is left without crucial usage context such as idempotency behavior, required field semantics, return values, or failure modes. This is a significant gap for a tool with destructive consequences.

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 0%, so the description must compensate. It names recipient, channel, currency, and amount—which loosely map to customerEmail/customerPhone, paymentChannel, currency, and amount—but leaves idempotencyKey, merchantTransactionId, and customer name fields unexplained. This is insufficient for an agent to correctly populate all 9 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 states the specific action: 'send money outward through ZEN,' which clearly identifies creating a payout. This also differentiates it from sibling tools like refund_transaction, capture_transaction, and create_payment_link, none of which move money outward as a payout. The verb and resource are unambiguous.

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 cautionary context ('Highest-risk destructive write') and a pre-use verification checklist (recipient, channel, currency, amount), which helps the agent proceed safely. However, it does not explicitly specify when to choose this tool over alternatives or mention any condition when it should not be used.

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