get_yield_curve

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

Annotations already declare readOnlyHint=true, and the description adds value by specifying exactly what data is included (the four tenors and the 2s10s spread). This goes beyond a generic 'get' and helps set expectations about the return payload, though it doesn't discuss data freshness or update behavior.

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 two sentences, front-loaded with the core functionality and then usage guidance. Every word earns its place with no redundant information or filler.

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 zero parameters, a read-only annotation, and an existing output schema, the description fully captures what the tool does, what data it returns, and when to use it. Nothing essential is missing for a simple market data getter.

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?

The tool has zero parameters, so there is nothing to explain. The schema coverage is 100% (empty schema), and the description correctly omits parameter details. Baseline 4 applies for a no-parameter tool.

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 returns the current US Treasury yield curve with specific maturities (2y/5y/10y/30y) and the 2s10s spread. This specific verb+resource combination distinguishes it from sibling market data tools like get_quotes or get_vix_panel.

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 gives use cases: 'Use for rates context, curve-shape regime, or to feed a duration scenario.' It doesn't mention when not to use or name alternatives, but the guidance is clear and actionable for an agent deciding to invoke this tool.

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