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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context about the data source and notes that row counts are approximate, but it does not disclose freshness, update cadence, or empty/failure behavior. This is adequate but not rich.

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?

A single dense sentence that places the key output terms first and contains no filler. The source qualifier 'OrbitWan Wanchain archive indexer' is relevant and is appended without bloating the sentence.

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 zero-parameter read-only tool, this is nearly complete: it names the resource, the source, and the three categories of returned information. The absence of an output schema is partly mitigated by these specifics, though exact units or the format of 'head' and 'progress' are left unspecified.

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 input schema has zero parameters with 100% coverage, so the baseline is 4; no parameter-level guidance is needed. The metrics mentioned in the description are return values, not arguments, so there is no semantic gap to compensate for.

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 identifies a specific status resource for the Wanchain archive indexer and enumerates the metrics returned: indexed head, genesis backfill progress, and approximate row counts. It lacks an explicit verb and does not contrast with the sibling get_chain_coverage, so it is clear but not fully differentiating.

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?

No guidance is provided about when to use this tool versus alternatives such as get_chain_coverage, nor are there any exclusions or prerequisites. The only usage signal is the read-only annotation and the status-oriented wording.

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