top_yield_farms

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

With no annotations, the description carries full burden. It mentions 'realistic APY (emissions stripped)' and 'risk notes', hinting at data processing, but does not detail calculation methods, data freshness beyond '24h', error handling, or potential limitations. Adds some context but lacks comprehensive behavioral disclosure.

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?

Two concise sentences that front-load the main purpose and key features. No extraneous information. Every sentence adds value.

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 simple list tool with 3 optional parameters and no output schema, the description covers purpose, data source, and key outputs. However, it lacks explanation of risk notes derivation, default limit, or pagination behavior. Could be more complete but is adequate.

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 100%, so baseline is 3. The description does not mention any parameters (limit, min_apy, asset) or explain their purpose beyond what the schema already provides. No added value over 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 clearly states the tool returns 'top DeFi yield farm picks' with specific attributes like 'realistic APY (emissions stripped), risk notes, TVL, protocol'. It specifies 'latest 24h' and the data source 'FalsifyLab daily aggregator', which distinguishes it from sibling tools like 'active_airdrop_farms'.

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?

While the description implies use for yield farming recommendations, it does not explicitly state when to use this tool versus alternatives like 'active_airdrop_farms' or provide any conditions or limitations. No guidance on prerequisites or exclusions.

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