pons_pay

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

With no annotations, the description carries the full burden and does well: it discloses the required PONSMCP_PRIVATE_KEY env var and the guards (policy limits, balance check, receipt verification). It stops short of stating irreversibility, behavior on policy/balance failure, or retry semantics for a real fund transfer.

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?

Front-loaded with the action and efficient overall, but the closing 'Guards: policy limits, balance check, receipt verification' partially repeats the flow already stated ('policy check … verify the on-chain receipt'). Mostly, not entirely, waste-free.

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-stakes mutation tool with no annotations and no output schema, the description covers the flow, credential requirement and guard rails. It omits what the tool returns and how failures surface, which an agent would benefit from knowing before sending funds.

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 payTo, amountUsd and waitMs (with default) are already documented in the schema. The description adds no parameter-level detail beyond that, so baseline 3 applies.

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?

States a specific verb and resource — 'Execute an autonomous MPP payment' — and names the exact asset and chain (USDG on Robinhood Chain). It is unmistakably a write/transfer tool, clearly distinguished from the read-only siblings (pons_price, pons_balance, pons_quote, pons_tx_status).

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 lays out the internal sequence (policy check → transfer → receipt verification), which implies usage context, but never says when to prefer this over siblings such as pons_quote or pons_tx_status, nor any precondition like 'obtain a quote first'. Usage is implied rather than stated.

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