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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds real value beyond that by stating 'no private keys required' (auth expectation) and describing the two shapes of returned data, which is what an agent needs to know before calling a wallet-scoped read.

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?

Three short sentences, front-loaded with the verb and resource, then returns, then safety, then the usage cue. Efficient overall; 'Read-only' modestly duplicates the readOnlyHint annotation, but the companion 'no private keys required' 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?

There is no output schema, so the description carries the burden of explaining return values, and it does so for both result categories. Minor gaps remain: nothing about behavior when the wallet holds zero positions, or whether results are paginated or cached, which matters for an openWorld tool.

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?

There is only one parameter and schema coverage is 100%, with the wallet parameter documented as a base58 Solana public key of 32-44 chars. The description's phrases 'positions' and 'wallet assets' imply both derive from that same wallet, but it adds no format or scoping detail beyond the schema. 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 names a specific verb and resource ('List all Raydium CLMM positions and wallet assets') and immediately enumerates what comes back (position NFTs with pool, ticks, liquidity; eligible input assets with balances). This separates it from per-position siblings like get_position_performance or get_position_range_status, though it doesn't name them 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?

'Use this first to discover available positions and assets' gives clear ordering guidance: this is the discovery entry point before quote_/prepare_ tools. It stops short of explicit exclusions or naming the alternative tools for deeper per-position queries, so the agent has context but must infer the boundary.

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