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

With no annotations, the description does substantial behavioral work: it discloses the exact charge, supported payment networks, lack of account or API-key requirements, failed-call billing policy, data source, and endpoint. It does not clarify payment mechanics, update cadence behind the claim of 'live' data, or rate-limit 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?

The description is compact and front-loads its paid nature and protocol-specific data scope, followed by cost, authentication, failure-billing, and endpoint details. There is virtually no filler, and the URL is placed last without obscuring selection-critical information.

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?

For a simple paid read with three optional parameters, the description and schema together cover scope, principal metrics, source, cost, authentication, and invocation defaults. Because there is no output schema, the absence of response-structure details, exact chain coverage, and a more precise freshness guarantee leaves minor gaps.

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?

All three optional parameters are already documented in the schema, including defaults and ranges, so the high schema coverage establishes a baseline of 3. The description clarifies what is being sorted and filtered but adds no concrete guidance about sort, limit, or min_tvl_usd beyond the schema.

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 precisely identifies the resource as Compound V3 pools across chains and names the returned metrics: APY, TVL, and seven-day APY change, sourced from DefiLlama. The protocol scope distinguishes it in substance from other yield tools, but it does not explicitly contrast Compound V2 or the chain, token, and top-yield siblings.

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?

The wording implies using the tool when current yield-pool data is needed specifically for Compound V3 across chains. It gives no explicit when-not guidance or conditions for choosing alternatives such as buy_yields_protocol_compound-v2, a chain or token yield tool, or buy_yields_top.

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