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

There are no annotations, so the description carries the full burden for behavioral disclosure. It does not mention whether the operation is read-only, how results are sorted or paginated, what 'top' means (e.g., by yield vs. TVL), or any defaults for the parameters. The description is too minimal to convey these important behavioral traits.

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 concise sentence with no fluff. It is front-loaded with the key purpose. However, it is slightly under-specified, lacking detail that could easily be added without making the description bloated, so it earns a 4 rather than a 5.

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 and no annotations, the description should explain return values, sorting, and possibly differentiate from siblings like base_protocol_tvl. It does none of this. The tool has only two parameters, but the lack of return format and selection criteria makes it incomplete for an agent to fully understand what it will get.

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 coverage is 0%, so the description must explain the parameters. It only addresses 'min_tvl_usd' implicitly through 'filtered by TVL' but does not explain 'limit' or its default behavior. The parameter meanings are not fully clarified beyond what the schema already shows (e.g., default values).

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 clearly states the tool lists top DeFi yield opportunities on Base, filtered by TVL. It is specific about the resource (DeFi yields on Base) and the action (listing top opportunities), and it distinguishes itself from sibling tools like base_gas or base_overview.

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 description provides clear context for when to use this tool: when the user needs top DeFi yield opportunities on Base. It does not explicitly mention alternatives or exclusions, but the purpose is distinct enough from siblings that the context is clear without needing to name them.

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