Search FRED series

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

With no annotations, the description carries full burden. It states it returns series with IDs, titles, and metadata, but does not disclose pagination behavior, the two search types (full_text vs series_id), or any rate limits. This is a significant gap for a tool with 10 parameters and no output schema.

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?

Three concise sentences, all relevant, with the most important information front-loaded. No redundancy or fluff.

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 10 parameters, no output schema, and no annotations, the description is too sparse. It lacks explanation of search types, pagination usage, ordering behavior, and any practical examples. An agent would need more guidance to use the tool effectively.

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%, so the baseline is 3. The description adds slight value by mapping 'keywords, tags, or filters' to search_text, tag_names, and filter_variable/filter_value, but does not explain other parameters like order_by or search_type beyond the 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?

Description clearly states it searches for FRED economic data series by keywords, tags, or filters, and returns IDs, titles, and metadata. This distinguishes it from sibling tools fred_browse and fred_get_series, as it's search-oriented rather than browsing or direct retrieval.

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?

Explicitly advises using this tool when you know what you're looking for, providing clear context for when it applies. However, it does not mention when to use alternatives (fred_browse or fred_get_series) or provide exclusions, so it falls short of a 5.

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