send_to_wallet_usd

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

No annotations are present, so the description carries the full burden; it does add real behavioral context that 'send' alone wouldn't — cost (free), speed (instant), and rail (intraledger). It stops short of the traits that matter most for a funds-moving mutation: irreversibility, failure modes for an unknown/invalid recipient wallet, insufficient balance, and whether a memo is exposed to the recipient.

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, zero waste, with the operation and its rail front-loaded and the unit caveat placed last where it lands as a reminder. Nothing redundant given the schema.

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 4-parameter fund transfer with no annotations and no output schema, the description establishes the rail and unit but says nothing about what is returned on success (transaction ID?) or what happens on failure. An agent can call it, but cannot predict the result.

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%, with every property documented including the cents unit and the ownership distinction between wallet_id ('your wallet') and recipient_wallet_id. The description's 'Amount is in cents' merely restates the schema, 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 ('Send USD (Stablesats) directly to another Blink wallet') and pins the transfer mechanics with 'intraledger', which cleanly separates it from the onchain and Lightning siblings (send_onchain_usd, pay_invoice, pay_lightning_address). An agent can identify the operation and its scope without opening the schema.

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 parenthetical 'free, instant, intraledger transfer' implies when to prefer this over the paid onchain/lightning paths, but that preference is never stated as guidance and no sibling is named. It also omits the practical precondition that recipient_wallet_id is a Blink wallet ID that must typically be resolved first (e.g. via lookup_user_wallet or send_to_username).

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