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

With no annotations, the description carries the behavioral burden, and it discloses a genuinely non-obvious trait: Aave V4 spokes sharing a liquidity hub are grouped under a composed parent while the API still keys each market on the spoke. That prevents misreading of returned identifiers. It lacks pagination or response-shape notes, so it is strong but not exhaustive.

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-loads the core definition before the hub-grouping nuance and the sibling exclusion. Every sentence carries information, though the composed-parent example adds a touch of density that could be trimmed.

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 and no annotations, so the description must orient the agent, and it does: it defines the resource, names the platforms, explains the hub-grouping keying quirk, and excludes a confusable sibling. Missing only return-format or pagination expectations for a list endpoint with a limit parameter.

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 all five parameters are already documented with defaults, ranges, and alias behavior (e.g. aave-v4 accepted as an alias). The description adds contextual framing about what a 'market' means but no parameter syntax beyond the schema, 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 ('List lending markets') and immediately defines what a market is across five named platforms (Aave/Spark pool, Aave V4 spoke, Compound Comet, Morpho Blue pair, Kamino K-Lend). It also explicitly distinguishes itself from the sibling get_market_overview, so an agent can route correctly without opening a schema.

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 names the alternative (get_market_overview) and states the condition that separates them: platform-wide totals across all vaults vs. individual markets. It also hints at filter routing (version=v4 with protocol=aave), but does not cover when to prefer get_market or search_vaults, so it falls short of a full when/when-not map.

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