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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It does not state whether data is cached, real-time, aggregated, or read-only. It also fails to mention any limitations, response structure, or whether the tool performs calculations. The listed categories are content, not behavior.

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, compact phrase that front-loads the purpose and lists key topics in order of importance. It contains no filler or redundant information, earning a top score for conciseness.

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?

Given the tool has no parameters, no output schema, and no annotations, the description provides a reasonable outline of the data covered (price, TVL, supply, Governing Council, protocols). However, it leaves ambiguity about what 'protocols' entails and does not clarify whether the data is current, historical, or aggregated. It is adequate for a simple overview but has room for improvement.

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 takes zero parameters, so the input schema (empty object) already exhaustively documents the interface. Per the rubric, a 0-parameter tool earns a baseline of 4. The description appropriately does not attempt to explain nonexistent parameters.

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 states the tool provides a Hedera ecosystem overview and enumerates specific data categories (HBAR price, TVL, supply, Governing Council, protocols). This distinguishes it from more focused sibling tools like hbar_account_info or hbar_network_stats. However, it lacks an explicit action verb such as 'get' or 'list', so it does not fully meet the 5-criteria standard.

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?

The description gives no guidance on when to use this tool versus the named alternatives. It does not mention any prerequisites, exclusions, or specific scenarios where the overview is preferred over more detailed tools. The word 'overview' implicitly suggests a high-level view, but no explicit comparison or alternative is provided.

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