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

Discloses behavior for unpaid calls (returns payment challenge) and no data (not settled), plus honest not_found, which goes beyond readOnlyHint annotation.

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 informative paragraph covering output, usage, and errors without excessive verbosity, though it is slightly long for the amount of new info beyond 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?

No output schema provided, but the description lists all returned fields (TVL, per-chain breakdown, category, token symbol, chain list, description, links) and covers error cases and cost, making it complete for agent use.

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?

Only parameter 'slug' has a description and example in the schema (100% coverage), so the description adds no additional parameter-specific meaning beyond the schema, warranting baseline 3.

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 it provides full detail for one protocol by slug, listing specific fields (TVL, per-chain breakdown, etc.), and distinguishes from sibling tool defi_protocols by saying 'Use it after finding a slug with the protocols list.'

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 instructs to use after finding a slug, and describes cost and behavior on unpaid calls and unknown slugs, providing clear when-to-use and constraints.

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