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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that junk-farm filters are built in, but it does not state data freshness, whether the operation is read-only, or what fields the returned pool includes.

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?

The description is a single well-formed sentence with the core action and scope front-loaded. The parenthetical adds useful filtering context without wasted language.

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?

For a one-parameter read lookup, the description covers the selection logic, chain scope, asset scope, and junk-farm filtering. Because there is no output schema, the returned pool fields are not specified, but the core return concept is clear enough for invocation.

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 input schema already documents the single 'asset' parameter with examples. The description adds only 'given asset symbol' and does not provide additional syntax, constraints, or interpretation beyond the schema.

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 states a specific verb and resource: 'Get the single highest-APY pool on Base for a given asset symbol.' The word 'single' also implicitly distinguishes it from the sibling list tools, which enumerate yields or vaults.

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?

The phrase 'single highest-APY pool' implies usage when an agent needs one best recommendation rather than a list. However, the description does not explicitly name alternatives such as list_base_yields or explain when not to use this tool.

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