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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the read-only sentence is largely redundant. However, the description adds useful behavioral context beyond the annotations: the specific endpoint, the 10-wallet input ceiling, the 1000-account result ceiling, and what is returned (reclaimable tokens).

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 short and mostly front-loaded with the endpoint and scope. It wastes a sentence restating the title and another reiterating the non-destructive behavior already covered by annotations, but it remains easy to scan.

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 rich annotations, 100% schema coverage, and an output schema, the description supplies the key missing context an agent needs: the exact endpoint, batch scope, input and output limits, and return meaning. Authentication/pagination behavior is not described, but pagination and limit are handled by the schema.

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 ownerAddresses are already documented in the schema. The description only summarizes the body as listing wallets and reinforces the 10-wallet/1000-account limits; it does not add syntax or format details beyond the schema.

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 resource and action: fetching Token-2022 and SPL dust accounts across multiple wallets. The 'batch' scope is clear and implicitly distinguishes it from the single-wallet sibling get-wallet-dust-accounts, though it does not explicitly name that or the related get-empty-accounts-batch alternative.

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?

Usage is implied by 'across multiple wallets' and the 10-wallet cap, but the description never states when an agent should choose this over get-wallet-dust-accounts or get-empty-accounts-batch. There are no explicit exclusions or prerequisites.

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