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

Annotations already establish readOnly/non-destructive/non-open-world safety, so the bar is lower, yet the description adds real behavioral detail: sort direction rules (fee ascending, others descending), that fee/room are PoS-only, and that exited validators trail the live rows newest-first. It stops short of explaining volume/pagination or auth context.

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?

Front-loaded with the entity and its fields, then filter/sort rules, then the exit-row ordering caveat. Dense but every clause carries information; a slightly long sentence about epoch selection slows it marginally but nothing is wasted.

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 list tool with no output schema and three simple params, the description covers what each row contains, how filtering/sorting behave, and the exit edge case. It is complete enough to call correctly, with only minor gaps around result size/paging.

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?

With 0% schema description coverage the description must carry the load, and it does: it defines sort semantic direction per field, the PoS-only constraint on fee/room, and explains the free-text 'status' parameter as epoch selection (selected / not selected / exit) plus the special exit-only behavior. This is meaning well beyond the raw enum lists.

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 (list) and resource (PoS validators and Storeman nodes) and enumerates the profile fields returned, so the scope is unambiguous. It implicitly contrasts with the singular get_validator sibling via 'Every ... node', but never names it explicitly, leaving sibling differentiation to inference.

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 explains how to narrow results ('Filter by type and status', sort options) which implies usage, but never states when this tool should be chosen over get_validator or when it should not be used. Context is implied rather than declared.

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