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

With no annotations, the description carries the behavioral burden. It adds useful context about the self-hosted headers.peck.to (Chaintracks) source, but it does not disclose caching, freshness, potential lag behind the canonical chain, or the exact response shape. This leaves some uncertainty for an agent relying on the tip being current.

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 two sentences with no filler. The core identity, source, and output fields are front-loaded, and the practical usage guidance is given in the second sentence. Every sentence earns its place.

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 simple zero-parameter read-only tool with no output schema, the description covers the essential return fields and provides a concrete use case. It is nearly complete, but specifying the response format/types and freshness behavior would make it fully turnkey.

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?

There are zero parameters, so the baseline of 4 applies; there is no schema burden for the description to compensate for. No parameter-level explanation is needed or provided.

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 clearly identifies a specific resource ('current BSV chain tip') and enumerates the returned fields: block height, hash, and time. It also names the serving infrastructure, making it easy to distinguish from siblings like peck_block_at_height, which targets a block at a specific height rather than the current tip.

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 an explicit, actionable use case: compare a post's block_height to the tip height to reason about recency. However, it does not mention alternatives or when not to use this tool, so it falls short of full routing guidance.

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