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

No annotations are provided, so the description carries the full burden. It does disclose that results are ranked movers returned in both directions with net flow, which is useful behavioral content, but it says nothing about sort order, whether gainers and losers are returned together, data freshness, or rate limits.

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?

A single dense sentence plus a short use clause, with the ranking/filtering scope front-loaded. Nothing is wasted or repeated from the schema.

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 an output schema present, return values needn't be described, and the description covers four of five parameters including the otherwise-unconstrained period values. The main gaps are the default semantics for limit and min_tvl, which remain only in the schema.

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 coverage is 0%, so the description must compensate, and it largely does: it documents chain, category, minimum TVL, and enumerates the period values (1 hour, 1 day, 7 days) that the schema leaves as a bare string with a default. Only 'limit' is left unexplained.

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?

States a specific resource (DeFi protocols ranked by TVL change) with a clear verb-like framing ('grew or shrank most'). It implicitly separates itself from raw-snapshot siblings like defi_protocols_tvl and chains_tvl by emphasizing rank deltas, but never names an alternative explicitly.

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?

'Use to see where capital is moving' gives an implied use case, but there is no guidance on when to pick this over defi_protocols_tvl or chains_tvl, and no exclusions. An agent must infer the selection criteria from the sibling names.

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