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

Beyond the read-only annotations, the description discloses that results come from stored anchors with no upstream read, which is useful operational context. It also explains what the check values mean and what stats are included, adding substantial behavioral context beyond the annotations.

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 dense and packed with output-field detail in a single long sentence, but the content is relevant and front-loaded. It could be easier to scan with grouping, but there is little wasted text.

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 appropriately explains the returned fields, check-state semantics and stats. Combined with the fully documented input schema, this gives an agent enough information to call the tool and interpret the result correctly.

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 dir, sort, limit and range with enums and defaults. The description does not add meaning about how these parameters combine or how range affects stats, so it meets the baseline for a fully described schema.

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 states a specific resource and scope: every anchored checkpoint for a segment across Base and Solana, with the per-height fields returned. It does not explicitly name a sibling tool or explain why this differs from adjacent read tools, but the anchor-timeline purpose is still much clearer than a generic read.

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 a clear use case: checking that the chain's state is anchored on time and consistently. It does not state when not to use the tool or point to alternatives, but the intended context is explicit enough for an agent to route correctly.

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