create_payment

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

Discloses key behaviors beyond annotations: amount conversion to paisa, auto-generated txn_ref, return fields (pp_ResponseCode/pp_ResponseMessage), and non-idempotency warning. No contradiction with annotations (readOnlyHint=false, idempotentHint=false).

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?

Three sentences: first states purpose, second clarifies key parameter behavior, third warns about idempotency. No wasted words, front-loaded with essential information.

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 all essential aspects: purpose, parameter conversion, idempotency, response format, and non-idempotency warning. For a 5-parameter tool with no output schema, this description provides comprehensive context.

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 baseline is 3. Description adds value by explaining amount unit (PKR to paisa), txn_ref auto-generation, and response details. However, some info repeats schema descriptions (e.g., 'converted to paisa automatically').

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 tool creates a JazzCash Mobile Wallet payment. Specifies verb 'Create' and resource 'JazzCash Mobile Wallet (MWALLET) payment'. Distinguishes from siblings like 'check_payment_status' and 'refund_payment' by focusing on MWALLET creation.

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?

Provides explicit warning: 'Money-moving and non-idempotent — do not retry blindly.' Also notes txn_ref auto-generation, guiding use when idempotency is needed. Lacks explicit mention of when to use versus siblings like 'create_mobile_account_payment'.

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