Yield-Opportunities (bezahlt, x402, Datafeed)

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

Discloses payment via x402 and agent-suitability, which adds value beyond schema. However, no annotations exist, so description should cover more behavioral traits like data freshness, rate limits, or side effects; it omits these.

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 with key info front-loaded (payment, functionality, risk profiles). No wasted words, but could be slightly more structured for complex tool.

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 no output schema, description mentions return fields (score, rank, reasons) but lacks exact structure or format. Parameters explained in schema fill gaps, but overall completeness is average.

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 6 parameters with descriptions (100% coverage). Description adds little beyond schema, only reiterating profile enum and scoring concept. Baseline 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 it provides ranked DeFi yield opportunities with score, rank, and reasons, distinguishing it from siblings like 'sample_yields' or 'screen_tokens' which may focus on different aspects. The verb 'bietet' (provides) and resource 'DeFi-Yield-Chancen' are specific.

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?

Description implies usage for scored ranking beyond APY sorting and mentions risk profiles, but lacks explicit guidance on when to use vs alternatives like 'sample_yields' or 'decide_token'. No 'when not to use' mention.

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