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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the $500K minimum TVL default applies consistently across listing, policy, and Turnkey, defines executionReady precisely (TVL qualifies AND wallet present on chain), and flags POLICY_SYNC_RECOMMENDED as advisory-only so agents do not treat it as blocking. It omits read-only confirmation, pagination behavior, and any rate-limit/caching notes.

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?

Three tight sentences with zero filler, and the most decision-relevant content (chain-scoped discovery plus eligibility field meanings) is front-loaded. The jargon and abbreviations ("$500K everywhere", "POLICY_SYNC_RECOMMENDED") make it dense but not padded.

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?

There is no output schema, so the description must sketch the return shape, and it does by naming the five result fields and explaining the two non-obvious ones. The remaining gap is behavioral detail an agent might want, such as result ordering/paging beyond the schema's limit cap, which is minor for a read-only list tool.

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 is 3. The description only reinforces the minTvlUsd default ($500K) and adds indirect meaning to chainId via "yield chains"; it adds nothing for asset, sortBy, limit, or verifiedOnly beyond what the schema already states.

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?

"Open Morpho yield discovery by chain" plus the enumerated result fields makes clear this returns a list of Morpho yield markets/vaults with eligibility metadata. It is distinguishable from get_yield_market_detail and rank_yield_markets by the word "discovery" and the field list, though it never names those 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?

Usage is only implied: you call it to explore markets by chain. There is no explicit when-to-use vs rank_yield_markets (ranking), search_vaults, or get_yield_market_detail (single market), and no statement of prerequisites beyond an incidental note that executionReady requires a wallet on that chain.

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