fred_search

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

Annotations already declare readOnlyHint=true, which covers the safety profile. The description adds no extra behavioral context about return format, pagination, or how results are presented. It is not misleading, but it does not go beyond the annotation and basic purpose.

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: a clear purpose statement followed by examples. Every word earns its place, and the front-loading of the purpose makes it immediately scannable.

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?

For a simple search tool with two parameters and no output schema, the description covers the basic operation and provides examples. However, it lacks any mention of what the results look like or how to follow up (e.g., using fred_series_info to get details on a found series), and no guidance on the limit parameter's consequences. This is adequate but not complete.

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 already documents both parameters (query='Keywords', limit='Max results (default 20)') with 100% coverage. The description adds value by giving concrete examples of query values ('GDP', 'unemployment', 'CPI', 'mortgage rate') and implicitly clarifies that limit is optional via its default. This goes beyond the bare schema descriptions.

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 'Search FRED series by keyword' which is a specific verb+resource. The examples ('GDP', 'unemployment', 'CPI') provide concrete use cases and help distinguish it from sibling tools like fred_series_info and fred_series_data.

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 gives clear context for when to use this tool (to search FRED series by keyword), but does not explicitly mention alternatives or exclusions. It is evident from the examples and naming that this is the search entry point, but no direct comparison to other FRED tools is provided.

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