Fund wallet : Obtain a link in order to fund your wallet of the desired amount using a credit card, or the Solana address of your wallet if you want to fund your account using Solana.

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

Annotations include readOnlyHint=true, indicating this is a read operation. The description adds context by explaining that it 'obtains a link' or provides a 'Solana address', which clarifies the tool's behavior beyond just reading data. However, it doesn't detail rate limits, authentication needs, or what the link/address is used for, leaving some behavioral aspects unclear.

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?

The description is a single sentence that repeats the title verbatim, which is redundant and not front-loaded with unique value. While it's concise, it wastes space by not adding new information beyond the title, reducing its effectiveness.

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?

Given the tool's complexity (funding operations), lack of output schema, and minimal annotations, the description is somewhat incomplete. It covers the purpose and methods but doesn't explain return values, error conditions, or integration details. With no output schema, more context on what to expect would be beneficial.

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?

The input schema has 1 parameter with 100% description coverage, clearly documenting 'amount' as 'Amount to fund in your wallet in USD'. The description doesn't add any parameter-specific information beyond what the schema provides, such as format details or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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?

Tautological: description restates name/title.

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 description implies usage when funding a wallet via credit card or Solana, but doesn't provide explicit guidance on when to use this tool versus alternatives like 'request_payment_link' or 'send_money'. It mentions two methods but doesn't specify prerequisites or exclusions, leaving the context somewhat vague.

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