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 the safety profile is covered. The description adds that this is a pure passthrough of one specific endpoint ('calls only ... and returns that response'), but says nothing about pagination behavior, result size caps, or rate limits.

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 opening 'Empty Accounts.' merely repeats the title, and the second and third sentences overlap in describing the same endpoint. The useful content (single-endpoint passthrough, Token-2022/SPL scope, rent-cleanup purpose) is present but could be stated in two sentences.

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?

With an output schema present, a fully documented input schema, and complete annotations, the description only needs to establish purpose and data scope, which it does. The remaining gap is routing between this tool and the very similar batch/dust-account siblings, which is a usage rather than completeness issue.

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 the schema already documents page, limit, sortByAsc, sortByDesc, and ownerAddress thoroughly, including the mutual exclusivity of the sort parameters. The description adds no parameter-level meaning beyond that, so the baseline of 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: fetches empty Token-2022 and SPL token accounts for a wallet via GET /v4/wallets/{ownerAddress}/empty-accounts. It does not, however, distinguish itself from close siblings like get-empty-accounts-batch, get-wallet-dust-accounts, or get-dust-accounts-batch, which appear to cover overlapping 'rent cleanup' territory.

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 only implied through the phrase 'Returns results to identify accounts eligible for rent cleanup,' which hints at the underlying goal without stating when to pick this tool over the batch or dust-account siblings. No exclusions, prerequisites, or explicit alternatives are given.

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