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

Annotations already establish readOnlyHint=true and openWorldHint=false, but the description adds substantial context beyond them: pagination bounds (limit 1-25), cursor semantics (next_cursor), the presence of stake-return entries labeled 'Stake returned', and the exited-validator edge case (status exit, live stake 0, history in flows). This is unusually rich behavioral disclosure for a read tool.

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 information-dense and front-loads the resource, but it reads as telegraphic notes strung together with semicolons ('Default profile. flows pages with limit...'), which hurts parseability. It is compact but not well structured.

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 no output schema, the description must explain returns, and it covers the key shape (found, type, name, next_cursor) plus notable edge cases. For a four-view query tool this is close to complete, though the payload of each individual view (e.g. rewards/profile fields) remains unsummarized.

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 0%, so the description must carry the parameter burden, and it largely does: it maps view values to node types (profile/rewards/flows for PoS; profile/flows/members for Storeman), states the default view, and gives the limit range (1 to 25) and the cursor's role (next_cursor). The required address parameter is never described, leaving a small gap.

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 (a Wanchain PoS validator or Storeman node) and the dimensions returned (profile, rewards, flows, members), so an agent knows this is a per-address node lookup rather than an enumeration. It does not explicitly contrast itself with the sibling list_validators, which slightly weakens differentiation, but the resource is unambiguous.

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 through the view-by-node-type mapping and the 'Default profile' note, but there is no explicit statement of when to use this tool versus list_validators or the get_address_* siblings. The agent must infer that this is the address-scoped validator lookup.

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