send_payment

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

Describes three validation/signing steps but does not cover error handling, idempotency, or transaction confirmation behavior. No annotations provided, so description carries the full burden.

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, front-loaded with purpose, no unnecessary words. Efficiently communicates key guidance.

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 purpose, usage, and behavior adequately for a payment tool with no output schema. Lacks return value description but otherwise 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 50% (expected_solana_recipient described, payment_request only type string). Description mentions validation of protocol fee and recipient address but doesn't explain payment_request structure or format.

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 tool pays a Solana payment request from provider job feedback, and distinguishes from siblings by recommending alternatives for auto-verification.

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 to prefer submit_and_pay_job or buy_capability, and to use send_payment only for manual flows with independently verified recipient addresses.

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