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

Annotations only declare read-only/idempotent/open-world; the description goes well beyond them, disclosing that liquidity-pool rates are fee income before impermanent loss, that missingSources means venues are absent rather than zero-yield, and that notCompared lists non-indexed venues. These are exactly the interpretive traps an agent would otherwise fall into when reporting numbers.

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 core purpose, then dense but non-redundant detail. The enumeration of returned fields is long, though it is justified because no output schema exists. No filler sentences, but the block is heavy to parse in one pass.

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?

With no output schema, the description carries the return-value burden and does so thoroughly: APR vs APY distinction, measurement basis and window, venue size, lock-up, risk tags, and one-year return in asset units. Combined with the missingSources/notCompared semantics, an agent has everything needed to call and report correctly.

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 both parameters are already documented, including the note that a large amount lowers a small venue's rate. The description adds only the framing "for a given amount" and the one-year return convention, so it sits at the baseline rather than adding new parameter meaning.

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 and resource ("Ranked comparison of the places ... can earn a return, for a given amount") and enumerates the venue classes covered (staking, Liqwid/Lenfi lending, FluidTokens P2P, DEX LPs). An agent immediately knows what comes back. It does not, however, distinguish itself from the sibling get_earn_rates, so sibling differentiation is left to inference.

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?

Gives clear context for use: compare yield venues for a specific holding and amount, and it explicitly tells the agent to caveat quoted rates as current/past readings rather than promises. What is missing is any exclusion or explicit routing rule against get_earn_rates, which appears to be the nearest overlapping sibling.

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