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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the bar is lower. The description adds that it calls only that one endpoint and returns the response verbatim, which is mildly useful, but says nothing about pagination caps, rate limits, or result volume.

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?

Four short sentences that front-load the endpoint and the resource. There is mild redundancy between 'Calls only GET ... and returns that response' and 'Solana API endpoint for fetching ...', and the leading 'Dust Accounts.' restates the title, but nothing is padded.

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 and annotations cover the safety profile, so the description only needs to establish what the tool hits and why. It does that; only secondary details like pagination behavior under the 1000-default limit or batch-tool tradeoffs are absent.

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%, so page, limit, sortByAsc/sortByDesc and ownerAddress are fully documented in the schema. The description only alludes to ownerAddress through the endpoint path, adding no new parameter meaning; 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?

States a specific verb and resource: fetching dust Token-2022 and SPL token accounts for a wallet, plus the concrete endpoint GET /v4/wallets/{ownerAddress}/dust-accounts. It does not explicitly distinguish itself from close siblings like get-wallet-empty-accounts or get-dust-accounts-batch, so it stops short of a 5.

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 phrase 'reclaimable tokens to identify accounts for rent recovery' implies the use case, but there is no explicit when-to-use guidance and no routing to alternatives such as the batch variant or the empty-accounts endpoint. Usage must be inferred from the purpose statement.

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