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

There are no annotations, so the description must explain behavior. It only lists the data categories (supply, nodes, consensus info) with no indication of whether this is a read-only call, whether results are cached, or any other operational traits. The read-only nature is implied by 'stats' but not explicitly stated.

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 a single short phrase, which is appropriately concise for a parameterless tool. It conveys the core purpose without unnecessary details, though it could be slightly more informative while remaining concise.

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, the description is the only source for expected return content. It names three categories (supply, nodes, consensus info) but does not explain their structure or depth. This is minimally sufficient for basic understanding but lacks detail for nuanced use.

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 tool has zero parameters, and the schema is an empty object. This achieves the baseline for parameter semantics. The description adds no parameter-related details because there are none to add.

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 the tool as providing network stats, specifying supply, nodes, and consensus info. This is specific enough to distinguish it from broader overview tools, though it lacks an explicit verb like 'get' or 'retrieve.'

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 given on when to use this tool versus its siblings. The description does not mention alternatives or any context that would help an agent decide between this and hbar_overview or hbar_protocol_health.

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