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

With no annotations, the description carries the behavioral burden well by disclosing the exact charge, USDC payment networks, lack of account or API-key requirements, no charge for failed calls, and the DefiLlama data source. It does not explicitly confirm that the call is read-only and does not itself open a DeFi position, and it omits freshness or rate-limit details.

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 information-dense, with paid status, purpose, metrics, source, cost, authentication, and failure billing each conveyed efficiently. Even the endpoint URL adds provenance without creating substantial clutter.

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 lookup with three optional, well-documented parameters, this supplies nearly all the operational context needed for correct invocation. With no output schema, the exact row structure remains unspecified, and explicit routing to alternative yield scopes would make selection more robust.

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 description coverage is 100%, so the baseline score of 3 applies. The listed APY and TVL metrics clarify the returned data, but the description adds no further syntax, defaults, or interaction guidance for sort, limit, or min_tvl_usd.

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 clearly identifies a live, protocol-scoped yield-pool lookup for Morpho Blue, including APY, TVL, and 7-day APY change. Its protocol-specific, cross-chain scope distinguishes it from the chain-, token-, stablecoin-, and top-yield sibling tools.

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?

An agent can readily select it when it needs current Morpho Blue pool yields across chains rather than yields filtered by a particular chain or token. However, it gives no explicit when-not guidance or named alternative for broader or differently scoped yield queries.

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