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

With no annotations provided, the description carries the full burden and does so well: it discloses the snapshot refresh cadence (every 15 minutes), that it is Celestia-only, the partial-name candidate behavior, and critically that validator names are user-typed and marked untrusted - a data-quality caveat an agent would otherwise not know.

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?

Every clause earns its place and the payload (what is returned) is front-loaded ahead of the lookup mechanics. It is a single dense paragraph, though, and the long field enumeration makes it slightly heavy to scan.

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?

There is no output schema, so the description correctly assumes responsibility for describing the return payload in detail, and it also covers input modes, networks, and data caveats. Nothing an agent needs to call it correctly appears to be missing.

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 50%; the validator param already documents 'operator address or validator name' in the schema, so the description partially echoes it, but it adds genuine meaning via the celestiavaloper prefix hint, the multi-match partial-name behavior, and the 'Celestia only' constraint. The undocumented network enum is clarified as 'Mainnet or the Mocha testnet'.

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 ('everything ... about one Celestia validator') and enumerates exactly what is returned, so the agent knows this is single-entity detail retrieval. It is cleanly separable from the sibling list_celestia_validators, which returns a collection rather than one entity.

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 invoke it - by operator address or name, with partial names returning candidate matches - and scopes it to mainnet or Mocha. It gives clear context for use but stops short of explicitly routing the agent away from siblings (e.g. 'use list_celestia_validators to enumerate, this to drill into one').

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