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

There are no annotations, so the description alone must disclose behavioral traits. It states what the tool returns, but does not explicitly confirm it is read-only, mention data freshness, or describe any side effects. It does not contradict annotations, but it leaves important safety and behavior information unstated.

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 a single, front-loaded phrase that packs significant meaning into few words. It avoids unnecessary filler and efficiently conveys the tool's purpose and key outputs.

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?

The description lists the primary outputs but leaves 'concentration analysis' undefined and does not clarify the response structure or measurement methodology. Since there is no output schema, the description should be more explicit about what the returned data looks like to be fully complete.

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?

The tool takes zero parameters, and schema coverage is 100% (no params to document). The description does not need to compensate for schema gaps, so the baseline of 4 is appropriate.

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 clearly identifies the tool as a validator overview and enumerates specific outputs (active/delinquent counts, top 10 by stake, concentration analysis). This distinguishes it from sibling tools like sol_network_stats, which likely focus on network-wide metrics rather than validator-specific data.

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 description provides no guidance on when to use this tool instead of alternatives such as sol_overview or sol_network_stats, nor does it mention any exclusions. The usage context is implied but not explicit.

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