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

With no annotations, the description carries the full burden, and it does disclose a genuinely important trait: the call costs $0.01 USDC, which the agent needs to know before invoking. However, it omits whether the operation is read-only, what happens for an unknown/empty wallet, and whether the payment is charged on failure.

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?

A single dense sentence with no filler, and the most decision-relevant fact given the space (the cost) is placed last for emphasis. It is efficient, though the front-loading favors output contents over what the tool actually does.

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?

There is no output schema, so the description must carry the return values, and it does list them (holdings, summary, windowed PnL, win rate, labels). But for a paid tool it leaves the failure/charging behavior and the address preconditions unstated, which an agent needs before spending $0.01 USDC.

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 description coverage is 100% and there is only one parameter ('address', documented as a Solana wallet address), so the schema already does the work. The description adds no meaning about the address beyond implicitly assuming it identifies the wallet whose profile is returned. Baseline 3 applies.

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 enumerates the payload (holdings, PnL, win rate, labels) but never states the action verb — it reads as a return-value list rather than 'fetch a wallet's profile'. An agent can infer the intent from the tool name and the single address parameter, but the purpose is implied rather than stated, and there is no differentiation from siblings like wallet_funding.

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?

No guidance on when to use this versus wallet_funding or token_trending, and no preconditions such as requiring a valid Solana address. The only usage-adjacent signal is the $0.01 USDC cost, which tells the agent it's a paid call but not when it's the right call.

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