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

Annotations already cover read-only, non-destructive and open-world semantics, and the description adds real value on top: data is scoped to the current user via API key and there is no way to query another user's wallet. It does not discuss caching, freshness, or why idempotentHint is false, but the added scoping and wallet-class caveats are substantive.

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 core definition and the deposit instruction, with the wallet-class warning emphasized. Slightly repetitive (the 'agentic wallets only' point is made twice) and the heavy caps/emoji styling adds length, but no sentence is wasted.

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?

An output schema exists, so return values need not be described; combined with zero parameters and read-only annotations, the remaining gaps an agent could face — scope, wallet class, which chain to deposit to — are all covered. Nothing needed to call it correctly is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The text correctly frames the implicit 'parameter' — whose wallets are returned — as fixed to the API key.

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 ('the user's AGENTIC wallets, with their addresses') and immediately narrows scope so the agent can distinguish it from the many other get_my_* tools. The explicit contrast with regular app wallets removes the most likely confusion at selection time.

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 actionable routing ('AI Trading is Solana only for now: tell the user to deposit to the Solana one') and warns that this is the source of truth for all other get_my_* data. It does not name a specific sibling to prefer for a different task (e.g. get_my_balances for balances), so it stops short of full when/when-not guidance.

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