fred_series_info

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

readOnlyHint already indicates a safe read operation. The description adds the specific metadata fields returned, which is helpful since no output schema exists. There is no mention of rate limits or other behavior, but the annotation covers the primary safety concern.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose and return content. No wasted words.

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 description is adequate for a simple metadata lookup tool, covering the key return fields. It omits details like return format or error behavior, but given the tool's simplicity and the presence of readOnlyHint, it is sufficiently 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 input schema already documents the sole parameter series_id with examples. The description adds no additional parameter semantics, but since schema coverage is 100%, the 3 baseline applies.

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 metadata for a FRED series, listing specific fields (title, units, frequency, range, notes). This differentiates it from siblings like fred_series_data (which likely retrieves time series values) and fred_search (which searches for series).

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 implies usage when one needs metadata for a known FRED series ID, but does not explicitly mention alternatives or exclusions. It does not state when to use fred_series_info versus fred_series_data, so guidance is inferred rather than explicit.

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