get_best_yield

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

No annotations provided, but description discloses scoring mechanism (9-signal algorithm, 13,800+ pools), output format (reasoning + 2 alternatives, ~60 tokens), and what the tool does not do (list all). Slight gap on side effects, but it's a read-only analysis tool.

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?

Well-structured with clear sections; every sentence is informative and necessary. Front-loaded with main purpose, then details, guidelines, and output size.

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?

Comprehensive for a DeFi yield selection tool: covers scope, algorithm, output, when/not to use, and parameter details. Output schema exists but not shown; description still feels 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?

Schema has 100% coverage with descriptions. Description adds context like risk_profile thresholds, amount_usd minimum TVL filter (10x), and chain examples, exceeding what schema 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?

Description clearly states it selects the single best DeFi yield opportunity for an asset and risk profile, distinguishing it from sibling tools like compare_yields and explain_risk.

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 provides 'Use this when' and 'Do NOT use for' sections, directing to alternatives (compare_yields, explain_risk) for other tasks.

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