send_to_wallet_usd

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

No annotations so description carries full burden. It discloses cost (free), speed (instant), and transfer type (intraledger), plus unit (cents). But doesn't mention prerequisites, failure modes, or what happens on insufficient balance.

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 concise sentences, front-loaded with action and key context. No filler.

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?

Simple tool with 4 params, no output schema. Description covers main purpose and transfer type but omits return value or error behavior. Adequate minimal description but not comprehensive.

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 covers 3 of 4 parameters with descriptions; memo lacks description. The description reinforces the amount unit but adds little beyond schema. Baseline 3 for high 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?

Clear verb 'Send' with explicit resource 'USD (Stablesats)' and target 'another Blink wallet'. Distinguishes from sibling onchain and Lightning transfer tools by noting 'free, instant, intraledger transfer'.

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?

Provides clear context: use for direct Blink wallet-to-wallet transfers. Mentions intraledger specificity, which excludes onchain and Lightning. However, it doesn't explicitly name alternatives or state when not to use it.

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