spectra_get_yield_curve

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

No annotations provided, so description carries full burden. It discloses automatic symbol normalization (USDC.e, WETH, wstETH → normalized), sorting by maturity, and implied APY calculation. However, it does not mention read-only behavior, auth requirements, or rate limits. Still, the behavioral traits are well communicated.

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 a brief headline, explanatory paragraph, and bullet-like usage guidance. Each sentence adds value. Front-loaded with main purpose. Could be slightly more concise by removing redundant phrasing, but overall effective.

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 the tool's complexity (cross-chain yield curve with normalization) and lack of output schema, the description sufficiently explains what the tool does and how it processes data. It omits output format details but provides enough context for an agent to understand the result type.

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 add much beyond schema for parameters; it provides context for 'underlying' and 'chain' in the usage paragraph. The schema descriptions are already clear. No additional semantic enrichment.

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?

Clearly states it shows the yield curve (term structure) for a given underlying asset across all chains. Specifies it fetches PTs, sorts by maturity, and displays implied APY. Distinguishes from siblings like spectra_get_pt_details and spectra_compare_yield.

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 describes when to use (fixed-income view, term premium analysis, maturity selection) and when not to (defers to spectra_get_pt_details, mv_check_ibt_health, spectra_get_pool_capacity, spectra_compare_yield for specific purposes). Provides clear alternatives.

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