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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine behavior beyond that: it discloses the ordering rule (categories low to high risk), the basis of the ranking (stated yield under published rules) and an explicit disclaimer that this is not a recommendation, which is exactly the kind of framing an agent needs before relaying results.

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 output shape and scope, then closed by the ordering rule and the 'not a recommendation' caveat, with no filler sentences. The middle sentence is dense but every clause (risk level, route, contracts, URL) tells the agent something about the result.

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 carry the return shape, and it does: risk level 1-5, purchase route variants, contracts and page URL, plus category ordering. It does not say what happens when max_risk excludes all picks in a category or how yield is denominated/refreshed, so a small gap remains for a zero-required-parameter read 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 ref, max_risk and per_category are already documented with types, bounds and defaults. The description adds no extra parameter meaning beyond what the schema provides; its value lies in the return-shape and ranking-rule explanation instead, so the baseline of 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?

The description names the exact resource and scope: per-category wallet-purchasable tokens with the highest stated yield 'right now', plus what each pick carries (risk level, purchase route, contracts, URL). That is far more specific than 'get yields', but it never explicitly positions itself against the search-oriented siblings such as search_yield_products or get_product_details, so the differentiation is inferred from the curation language rather than stated.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named. Usage is only implied by the content (a curated per-category ranking of currently purchasable high-yield tokens), so an agent must infer that this is a discovery shortcut rather than a query interface.

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