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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by specifying exact metrics and time windows (last hour, last day, per minute) plus the unique 'nest behind chain' measure, though it does not disclose return shape, gas price units, or data freshness.

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 compact sentence lists every available data point with no filler. Each metric earns its place, and the most prominent items are front-loaded.

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 parameterless read-only snapshot tool, the description covers what data the agent will receive, including specific windows and units for ETH. Minor gaps like exact return structure or gas price unit prevent a 5, but nothing an agent needs to choose and invoke the tool correctly 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?

There are zero parameters, so the schema already makes all parameter requirements explicit at 100% coverage; parameter-level description is unnecessary. Per the baseline for zero-parameter tools, this scores 4.

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 enumerates a specific set of current Robinhood Chain metrics (block time, gas price, eth in dollars, launches, graduations, trades per minute, nest lag), making the tool's purpose clear. However, it lacks an explicit verb such as 'get' or 'list' and does not name sibling alternatives, so it doesn't fully distinguish itself from related tools.

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 explicit when-to-use or alternative routing is given, but the metric list and 'right now' title imply this is the snapshot tool for current chain-wide status. Since sibling tools like moving_now and graduating_soon cover related concepts, explicit exclusion or alternative guidance would have been valuable.

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