Fund the app wallet from this agent's identity wallet

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

Beyond the annotations (destructiveHint=false, openWorldHint=true), the description discloses that this is REAL-MONEY and gated, that it is the one signature the app-wallet model requires, that it needs a keypair and is signed locally, and that keyless/API-key users must use the web app. That is substantial non-obvious behavioral context the annotations alone do not convey.

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-loads the critical 'REAL-MONEY (gated)' warning and stays dense with operative facts. It is on the longer side and the final alternative-path sentence is slightly tangential, but nearly every sentence carries useful information.

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 real-money mutation tool with no output schema and sparse parameter documentation, it covers the safety profile, keypair requirement, keyless fallback, amount units, and an alternative funding path. It does not describe the result of a successful call, a minor gap given there is no output schema.

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 only 33%, so the description must compensate. It does so for sol/usdc by stating amounts are human units and giving concrete examples (usdc 12.5, sol 0.05), but it says nothing about confirmPhrase, which is only documented in the schema itself.

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 precise verb and resource: move USDC/SOL from the agent's own wallet into the app wallet. It clearly distinguishes itself from siblings like app_wallet_withdraw, withdraw_asset, and deposit by naming the source and destination wallets explicitly.

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?

Gives explicit conditions: use when the app wallet needs to pay for launches, deposits and fees; must be signed locally with a keypair; in KEYLESS mode go to the web URL instead. It also names an alternative path (plain USDC/SOL transfer from any wallet), so both when-to-use and alternatives are covered.

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