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

Annotations already cover readOnly/openWorld, and the description adds meaningful context beyond them: x402 payment model, price ($0.002 USDC) across Base/Solana/Arc, the fact that failed calls are free, and a data-coverage caveat. This is rich behavioral detail, though it omits error/empty-response behavior.

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?

Front-loaded with the core purpose and return fields, then payment and coverage notes. It is dense and each sentence adds value, though the pricing/billing detail is slightly verbose for a definition-level field.

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-value explanation isn't required, but the description still summarizes them; annotations cover safety and the description covers payment and coverage limits. Nearly complete, missing only error/empty-result expectations.

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 100% and the single protocol parameter is fully documented in the schema with the same 'lowercase slug' guidance. The description adds no parameter meaning beyond what the schema provides, so the baseline 3 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?

States a specific verb+resource: token vesting/emission unlocks per allocation label from DefiLlama emissions, by protocol slug. It also enumerates the return fields (last unlock, next scheduled unlock, total unlocked), which clearly distinguishes it from siblings like crypto_defillama_yields or tvl_oracle.

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?

Usage is implied by the purpose (vesting/unlock questions) and it flags a prerequisite-like caveat that coverage depends on DefiLlama having the protocol's emissions file. However, it never explicitly says when to prefer this over sibling DefiLlama tools, so routing guidance is only implicit.

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