request_payment

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

Discloses that spend policy may trigger approval, which is critical. Missing details on idempotency, failure modes, or return behavior. Adequate given no 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 paragraphs plus args list are efficient and front-loaded. No wasted words, but the args list is somewhat redundant with schema. Good overall.

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?

Missing return value description (e.g., payment request ID) and lacks comparison with sibling pay_x402. Incomplete for a payment tool with no output schema.

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?

Adds full meaning for all 4 parameters (recipient as 0x address, amount in whole units, reason for audit log, asset with default and token symbol). Compensates for 0% schema coverage.

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 'Request to pay an address' and 'send a payment,' but does not explicitly differentiate from sibling tool pay_x402. Purpose is strong but lacks sibling contrast.

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?

Explicitly says 'Use this whenever you need to send a payment; do not attempt to move funds any other way,' providing clear context. Does not specify exclusions or compare with pay_x402.

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