create_voucher

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

Description adds 'money-moving and non-idempotent,' confirming annotations. It also reveals the voucher is redeemed offline (no redeem API) and that the response includes a voucher number, providing behavioral context beyond annotations.

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?

Two dense sentences: first defines purpose and currency, second explains workflow and idempotency. No fluff, front-loaded with key info.

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 payment tool with 6 params (3 required) and no output schema, the description gives essential output hint (voucher number) and offline redemption flow. Lacks error handling or permission details, but adequate given context signals.

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 covers 100% of parameters with descriptions. Description only adds 'amount is in PKR rupees' which is redundant with schema's 'Voucher amount in PKR rupees.' No new semantic value beyond schema.

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?

Description clearly states the tool creates a JazzCash OTC voucher payment, with specific verb and resource. It distinguishes from sibling tools like create_payment or create_mobile_account_payment by specifying 'Over-The-Counter (OTC) voucher'.

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 usage for one-time offline voucher payments and notes non-idempotency, but does not explicitly compare to siblings or state when not to use this tool. Lacks explicit when-to-use vs alternatives guidance.

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