Get recently updated series

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

With readOnlyHint and openWorldHint annotations, the safety profile is already established. The description adds behavioral context by specifying the sorting behavior and demonstrating filter usage. No contradictions with annotations detected.

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?

Two sentences total – a clear statement plus an example. No wasted words; front-loaded with the core action.

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 output schema exists and annotations cover read-only behavior, but the 7-parameter schema with no descriptions leaves gaps in understanding time filtering and pagination. The description gives a single example but doesn't explain parameter semantics or return format. Given the tool's complexity, a slightly richer description would improve completeness.

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 has 0% description coverage, so the description must compensate, but it only mentions filter_value in the example. Other parameters like start_time, end_time, realtime_start, realtime_end, limit, and offset are not explained at all. The example adds some meaning to filter_value but leaves the majority of parameters undocumented.

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 states 'List FRED series sorted by when observations were last updated' – a clear verb+resource+sort criterion. This distinguishes it from sibling tools like search_series or get_series by focusing on update recency. The example reinforces the intended use.

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 provides clear context for when to use this tool (when you need recently updated series) but does not explicitly mention alternatives or exclusions. The example adds practical usage context. Overall, it implies the use case without explicitly contrasting against siblings.

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