pendle_get_yield_curve

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

No annotations are provided, so the description carries full burden. It explains the tool fetches and aggregates data across chains, filters by TVL/liquidity, and has a compact mode. However, it does not explicitly state that it is a read-only operation, though 'Show' implies no mutation. Missing explicit safety disclosure.

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 well-structured: first line summarizes, then details, use cases, and sibling differentiation. It is front-loaded and every sentence adds value without unnecessary verbosity.

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, the description explains the output (implied APY at each maturity) but does not specify the exact format (e.g., list of objects). It covers parameter semantics and usage well. A bit more detail on return structure would increase completeness.

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% with descriptions for all 5 parameters. The description adds context beyond schema: explains underlying with examples, chain behavior when omitted, and compact mode output. It also mentions sorting by maturity and displaying implied APY, which is not in schema.

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 the tool shows the yield curve for a given underlying asset across Pendle chains, specifying it fetches active markets, sorts by maturity, and displays implied APY. It distinguishes from siblings like pendle_get_market_details and pendle_get_market_capacity.

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 explicitly provides when to use the tool (fixed-income view, spot anomalies) and when to use alternatives (drill into maturity, check capacity, compare to Spectra). It also mentions the Pendle equivalent of spectra_get_yield_curve.

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