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

With no annotations, the description carries the full burden and does so richly: it discloses the measured fields, the interpretation rule (not signing a blob is not a failure when the publisher already had 2/3; only 'not ready' is), and warns that validator-typed names/hosts/certificate names are untrusted. This is substantive context well beyond what structured fields provide.

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 core purpose and information-dense throughout, with no filler sentences. The first sentence is unusually long and crams many clauses together, slightly hurting scannability, but every clause carries meaning.

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 6-parameter, no-output-schema tool, the description adequately covers what is returned, how to look it up, the optional sections, and interpretation caveats. Minor gaps remain (pagination/limit behavior for blobs, error semantics), but nothing essential is 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 100%, so the schema already documents all six parameters (baseline 3). The description adds meaning by spelling out what each include section contains (status=ready right now, history=hourly uptime/round trip, blobs=which blobs signed/not needed/could not, checks=latest download checks) and the accepted lookup forms, exceeding the schema text.

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 (retrieves/measures) and resource (one Celestia validator's Fibre Network Monitor data on mocha-5), and enumerates the exact dimensions measured. It is clearly distinguishable from list_fibre_validators (which it names) and from the broader get_celestia_validator.

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?

It gives lookup keys (name, celestiavaloper..., celestiavalcons...) and routes to list_fibre_validators for discovery, plus explains when to add the optional include sections. It does not explicitly contrast against get_celestia_validator or state exclusions, so it falls short of full when/when-not guidance.

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