wallet_funding_request

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

No annotations are provided, so the description carries the full burden; it does disclose the most safety-relevant trait — generation is local and no signature or transfer is submitted. It stops short of stating whether the wallet must already exist locally or whether any RPC/network access occurs.

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, artifact and safety boundary front-loaded, with zero filler. Every clause earns its place.

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?

With no annotations and no output schema, the description needs to cover more. It handles the destructive-action question well but leaves the return shape (URI string plus SVG payload?) and the expectedChainId guard behavior unstated.

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 0%, so the description must compensate. It implies the asset (Base USDC) and therefore the chain, but does not define the amountUsdc format (units, decimals, string encoding) or what expectedChainId actually guards against (presumably a mismatch check). Partial compensation only.

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 gives a specific verb (generate) and precise artifacts (Base USDC EIP-681 funding URI and SVG QR), which is far more informative than a generic 'funding request'. An agent can distinguish this from wallet_address or wallet_receive_info because the output artifacts are named exactly.

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?

Usage is implied by the artifact produced, and the boundary statement 'does not sign or submit a transfer' tells the agent this is a non-transactional path. However, no sibling alternatives (e.g., wallet_receive_info) or selection conditions are named, so the agent must infer when to pick this over adjacent tools.

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