Yield-Sample (kostenlos, Datafeed)

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

Discloses rate-limiting and free nature, but with no annotations provided, it lacks detail on read-only status, authentication needs, or side effects. Acceptable for a simple datafeed sample, but could be improved.

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: the first explains what the tool does and returns, the second states its ideal use case. No redundancy, perfectly front-loaded.

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?

Provides enough context for a simple tool: explains output (top pools plus 3-item preview with scores/reasons), mentions rate limit, and references the paid alternative. Missing mention of ordering or data freshness, but adequate for its purpose.

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 covers all parameters with descriptions (100% coverage). The tool description adds no additional parameter-specific details beyond the schema, so baseline score of 3 is appropriate.

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?

Description clearly states the tool provides a free, rate-limited sample of top DeFi yield pools plus a 3-item opportunity preview with scores and reasons. It explicitly distinguishes itself from the sibling 'yield_opportunities' as a free precursor, using specific verbs and resource names.

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?

Explicitly says 'Ideal vor einem bezahlten yield_opportunities-Aufruf' (Ideal before a paid yield_opportunities call), indicating when to use this tool. While it doesn't exclude other siblings, the context is clear for its primary role as a free trial.

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