defi_get_yields

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

With no annotations, the description carries the burden of indicating safety and behavior. The word 'Get' implies a read-only operation, and the filtering behavior is mentioned. However, it does not disclose return format, whether results are limited or paginated, or whether data is current vs historical.

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 two short, front-loaded sentences. Every word adds value: the purpose, scope, and available filters. No filler or redundant restatement of the tool name.

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?

The tool has four optional parameters, no output schema, and no annotations. The description explains what data is returned at a high level and lists filters, but it lacks details about response shape, default behavior when no filters are provided, or possible large-result pitfalls. This is adequate but not complete.

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 schema provides full descriptions for all four parameters, so the baseline is 3. The description adds natural-language context for 'chain', 'project', and 'minTvl', but omits mention of 'minApy'. It does not meaningfully extend the parameter semantics beyond what the schema already provides.

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 a specific verb and resource: 'Get yield/APY data for DeFi pools across all protocols.' It also lists the main filtering capabilities, distinguishing it from the singular defi_get_yield_pool sibling and other DeFi data tools.

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 gives clear usage context: it is for fetching yield/APY data across all protocols, with optional filters by chain, project, or minimum TVL. It does not explicitly name alternatives or provide when-not-to-use guidance, but the broad scope implies when this tool is appropriate.

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