DeFi yield finder

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

The description discloses the paid nature ($0.01 USDC per call) and payment mechanism, which is useful. However, it does not state whether the tool is read-only or disclose other behavioral traits like rate limits or authentication needs, lacking completeness.

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 concise with two sentences: the first states the purpose, the second adds cost information. Every sentence is necessary and front-loaded with key information, no fluff.

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?

Given the absence of an output schema, the description misses details about the return format, such as whether results are sorted or paginated. It covers the basics but is incomplete for an agent to fully understand the output.

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?

The input schema has 100% description coverage, so the baseline is 3. The description merely restates the filter options (symbol, chain, safety) already in the schema, adding no new constraints or format details.

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 explicitly states 'Find yield/farming opportunities' with optional filters, clearly indicating the tool's function. It distinguishes from siblings like defi_tvl which focuses on TVL, making the purpose specific and unambiguous.

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 implies usage for finding yield opportunities with filters, providing clear context. However, it does not explicitly mention when not to use it or suggest alternatives like defi_tvl for TVL queries, so it lacks explicit exclusions.

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