fred_series_info

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

Annotations already declare readOnlyHint=true, so the description adds value by listing returned metadata fields. However, it does not disclose any additional behavioral traits such as rate limits, data freshness, or handling of invalid series_id. The description is adequate but not enhanced beyond the annotation.

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?

Single sentence, directly states purpose and key fields. No extraneous words. Front-loaded with purpose. Every word earns its place.

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 metadata tool with no output schema, the description lists the key return fields (title, units, frequency, range, notes), which is helpful. It could be more exhaustive, but the given fields cover the most common needs. Absent output schema, this is reasonably 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?

Schema description coverage is 100%, and the parameter series_id is described with examples. The description adds no additional meaning or constraint beyond the schema, so a baseline of 3 is appropriate.

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 the tool gets metadata for a FRED series, listing specific fields (title, units, frequency, range, notes). The verb 'Get' and resource 'FRED series metadata' are specific, and given siblings like fred_series_data and fred_search, the purpose distinguishes this tool as returning metadata rather than 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?

No explicit guidance on when to use this tool versus alternatives. However, the name 'info' versus 'data' and 'search' implies it's for metadata retrieval. The context of siblings provides implicit differentiation, but the description lacks direct when/when-not statements.

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