get_fx_timeseries

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

The description only states it retrieves data, implying a read-only operation, but does not elaborate on behavior such as error handling, data ordering, or limitations. With no annotations, more detail is needed.

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 sentence of 10 words, highly concise and without fluff. However, it could benefit from a slight structure, but given its brevity, it is efficient.

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?

An output schema exists, so return format need not be described. However, the description lacks context about source (e.g., what constitutes a source) and does not clarify that data is most recent N points. It is minimally adequate but missing some context.

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 0%. The description explains last_n implicitly as 'most recent', but source is not described at all. The default and constraints for last_n are not mentioned.

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 it retrieves historical buy/sell series for a source, with a specific parameter for most recent N. This distinguishes it from sibling tools like convert, get_fx_quote, get_fx_stats, list_fx_sources, and reconcile, which have different purposes.

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 guidance is provided on when to use this tool versus alternatives. It does not specify prerequisites, exclusions, or context for choosing this over get_fx_quote or get_fx_stats.

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