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

The description discloses that the output is ranked by TVL, which is a useful behavioral detail. However, with no annotations provided, it does not clarify the return format, any potential limits, or that it is a read-only operation, though this is a simple list 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?

The description is a single, concise sentence that is front-loaded with the key information. Every word contributes meaning without unnecessary filler.

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, parameterless list tool, the description is sufficiently complete—it states the scope ('All Hedera DeFi protocols') and the ordering ('ranked by TVL'). No output schema exists, but the return values are implicitly clear for a ranked list.

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, so the schema trivially covers all inputs. The description adds no parameter details, but none are needed. The baseline of 4 for zero-parameter tools applies.

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 resource (Hedera DeFi protocols) and the ranking by TVL. It distinguishes itself from sibling tools like hbar_defi_yields and hbar_protocol_health, though it lacks an explicit action verb like 'list' or 'show'.

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 provided on when to use this tool versus alternatives. The description is purely descriptive with no mention of use cases, exclusions, or comparisons to sibling tools.

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