treasury-yields

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

No annotations are provided, so the description carries full burden. It discloses the data source (CBOE indices), that it's free and requires no API key, and the output elements. However, it does not mention behavioral aspects like update frequency, latency, or error handling, which are relevant transparency details.

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 sentences, no wasted words. The first sentence states the core function, the second adds derived metrics and use cases. Efficient and front-loaded.

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 parameters and no output schema, the description sufficiently covers what the tool returns (nodes, spread, classification) and its applications. It is complete enough for an agent to select and invoke correctly.

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 baseline is 4 per instructions. The description adds value by explaining the output: specific yield nodes, 10Y-3M spread, and curve shape classification, which goes beyond the empty 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 returns current US Treasury yield curve at specified nodes (3M, 5Y, 10Y, 30Y) from CBOE indices, with additional spread and classification. The verb 'Returns' and resource definition are specific, distinguishing it from sibling tools like treasury-auction-calendar.

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 provides clear use cases ('Essential for DCF discount rates, bond pricing, and recession signal monitoring'), guiding when to use the tool. However, it lacks explicit exclusions or comparison to siblings like credit-spreads.

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