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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that the result blends yield discovery with gas timing — useful context but no detail on freshness of data, chain coverage, or how the two signals are combined.

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?

A single front-loaded sentence with no filler or repetition. It is appropriately sized, though it could spend a few more words on the routing conditions that the sibling list makes necessary.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, with ~70 sibling tools and several near-neighbours, the definition omits the routing guidance and scope detail an agent needs to pick it confidently.

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?

Only one optional parameter (chain) with 100% schema description coverage ('EVM chain (default: base)'), so the schema already carries the semantics. The description adds nothing about supported chains or what happens when chain is omitted, which is exactly the baseline-3 situation.

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 ('Find') and a composite resource ('best DeFi yield opportunity combined with optimal gas timing'), which distinguishes it from single-purpose siblings like defi.yields or gas.optimize. The word 'best' is left undefined, so the exact optimisation criterion is not clear, but the tool's role as a yield+gas synthesiser is legible.

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?

No indication of when to prefer this over the many adjacent siblings (defi.yields, defi.farming, defi.compare, gas.optimize, gas.predict). An agent must guess whether this is an aggregate entry point or a narrow query. No prerequisites or exclusions are given.

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