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

No annotations are supplied, so the description carries the burden; it discloses the upstream sources (CoinGecko, mainnet RPC), the live/read-only nature of the call, and temporal scoping ('24-hour change', 'this epoch'). It does not mention caching, latency, rate limits, or what happens when an upstream source fails, which are the remaining behavioral gaps for a live-fanout tool.

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 timeframe and read mode, then the payload, then the routing sentence — no filler. The payload enumeration is dense and the opening is a grammatical fragment ('NEAR right now, read live'), but every clause carries information an agent needs.

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?

With no output schema and no annotations, the description must communicate both what comes back and how it is safe to call; it does the former via the field enumeration and the latter via 'read live' and the source disclosure. Only failure/degradation behavior for the external price and RPC dependencies is left unstated.

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?

Zero parameters, so the baseline is 4; the description confirms this with 'No arguments,' leaving nothing for an agent to infer about inputs.

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?

Specific verb+resource ('read live' NEAR state) with an enumerated payload: price/market cap/24h change from CoinGecko plus block height, protocol/node version, total supply and stake distribution from mainnet RPC. It explicitly distinguishes itself from get_validators and get_protocol_status, so an agent can route without opening a schema.

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?

Names both alternatives and the condition that selects each: 'For who the validators are, use get_validators; for the protocol upgrade vote, get_protocol_status.' It also states 'No arguments,' removing any invocation ambiguity.

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