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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral details: hourly refresh, historical percentile basis (8.7 years), and the Gold tier requirement for history in the parameter description. This surpasses minimal annotation coverage and helps the agent understand data freshness and access constraints.

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 first sentence is dense but information-rich, and the usage guidance is explicit. 'Updates: hourly' is a minor standalone clause, but overall the description is well-organized and wastes no words. It could be slightly more compact but remains efficient.

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?

No output schema exists, and the description compensates by listing all key output fields (trend, confidence, top drivers, chains-above-floor count, 30-day mean/change, percentile rank). It also provides data source, methodology, refresh cadence, and use cases, making it fairly complete for a read-only metric tool.

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?

Schema description covers 100% of the single optional parameter, explaining its behavior (history series) and the Gold tier requirement. The description itself doesn't add parameter-level details, so the baseline of 3 is appropriate given schema coverage.

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 specifies a precise metric ('0-100 DeFi liquidity breadth score'), defines its derivation ('count of top-20 chains with TVL above $100M, DeFiLlama data'), and lists output components, making the tool's function unmistakably clear. It goes beyond a vague verb+resource statement.

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?

Explicitly enumerates triggering user intents ('DeFi health', 'cross-chain TVL distribution', 'multichain liquidity concentration') and a strategic context ('timing cross-chain LP deployment'). It does not name alternative tools or exclusions, so it falls short of the full 5 but provides clear usage context.

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