get_chain_tvl_history

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

Discloses return format (array of {date, tvl}) and parameter behavior (empty chain for total). Without annotations, description covers key aspects but lacks info on caching 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?

Concise with clear Args/Returns sections, no redundant information. Every sentence adds value.

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?

Complete for a simple tool: explains return format, all parameters with defaults and constraints, and references a sibling tool. No output schema, but description fills the gap.

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?

Adds substantial meaning beyond schema: chain empty for combined TVL, days range 1-3650, default 90, and regex validation. Schema coverage is 0%, but description fully compensates.

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?

Clearly states the tool retrieves historical TVL for one chain or all DeFi combined, with specific verb 'Get' and resource 'historical total DeFi TVL'. Distinguishes from sibling 'get_global_defi' by noting it complements that tool.

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?

Provides explicit usage examples ('Ethereum TVL over the last year') and contrasts with 'get_global_defi' (only current number). Also specifies parameter constraints like chain validation and days range.

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