rates

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

No annotations are present, so the description must disclose behavioral traits. While it identifies the data source (FRED), it omits details such as read-only nature, data freshness, rate limits, or any potential side effects. This leaves the agent uninformed about operational characteristics.

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 contains a redundant repetition of the same sentence, making it inefficient. The example line adds some value but overall the structure wastes space without additional informative content.

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?

The tool has no output schema, so the description should explain the response format or structure. It only mentions yields and spreads but fails to describe what the output looks like (e.g., object with keys, units). This lack of completeness hinders the agent's understanding of the tool's result.

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 schema covers 100% of parameters with a description for 'series', so a baseline of 3 is appropriate. The description does not add additional meaning or context beyond the schema, such as default behavior or how the parameter affects the output.

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 specifies the tool provides US Treasury yield curve data and recession-indicator spreads from FRED, with explicit time ranges and spread types. The purpose is well-defined, though it lacks an explicit verb like 'get' or 'fetch' and does not differentiate from siblings, which are all distinct tools.

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?

No guidance is provided on when to use this tool versus alternatives, nor any preconditions or exclusions. The description merely states what the tool does without contextual usage advice.

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