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

The description adds 'Nothing is closed or moved' and 'Returns counts and net figures in SOL,' which goes beyond the read-only/idempotent/non-destructive annotations by clarifying outcomes and return type. The schema parameter description further reinforces the public, connection-free nature of the call.

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?

Two tight sentences front-load the action and scope, then add the key safety qualifier. Every phrase earns its place, with no repetition of the title or schema.

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?

For a simple single-parameter read tool with no output schema, the description covers the input, the read-only nature, the type of result, and the absence of side effects. It stops short of fully spelling out the exact return fields or when to prefer a sibling, but nothing essential is missing for calling it correctly.

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 coverage is 100%, and the parameter description already explains the address as a base58 public key with no connection/signature. The tool description adds no significant parameter semantics beyond that, so the 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 uses a specific verb ('Read') and a precise resource: reclaimable SOL rent from empty token accounts plus post-rent-cut surplus. This clearly distinguishes it from the other check_* siblings, which target different account/program concerns, even though no sibling is named.

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 intended use is implied: call it when you want to know how much rent a Solana wallet can reclaim. However, it gives no explicit when-not-to-use guidance or comparison with sibling check tools, so routing is left to inference.

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