pay

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

No annotations are provided so the description must carry behavioral burden. It implies a mutation (transfer), but doesn't mention whether the operation is irreversible, whether funds are held, authorization requirements, failure modes, or the significance of idempotency_key. It adds some context on mutability but leaves important behavior undisclosed.

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 short sentences front-load the core action and then provide use context, with no wasted words.

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 financial transfer with no annotations and no output schema, the description is incomplete: it omits error handling, partial failure semantics, and return behavior. It covers the core action but leaves significant gaps an agent would need to call it safely.

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 description coverage is 100%, so baseline is 3. The description adds no additional parameter meaning beyond what's already documented in the schema's 'amount' example and 'idempotency_key' purpose.

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: 'Transfer funds from one agent wallet to another.' This distinguishes it from siblings like fund_wallet (deposits in), release_payment (escrow release), and get_balance (read), making the purpose unambiguous.

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 phrase 'Use when an agent needs to pay for a completed task or service' gives implied usage but doesn't say when not to use it or name alternatives like release_payment or fund_wallet. For an agent deciding between payment tools, this is minimal guidance.

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