forex_get_grouped_daily_bars

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

No annotations are provided, so the description must carry the burden. 'Get' implies a read-only operation, but the description does not disclose the potentially large response size, pagination, or the effect of the 'adjusted' parameter. It adds minimal behavioral context beyond the basic operation.

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 essential operation. Every word contributes meaning with no redundancy or unrelated information.

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?

With no annotations and no output schema, the description should provide more context about the return format and the 'adjusted' parameter. It states OHLC is returned, but the scope of 'entire forex market' and potential pagination are unclear, leaving the tool under-specified for an agent to fully anticipate the response.

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 0%, and the description compensates only for the 'date' parameter by specifying the format YYYY-MM-DD. The 'adjusted' boolean parameter is not explained, leaving its meaning ambiguous. The description adds value for one parameter but ignores the other.

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 daily OHLC data for the entire forex market on a specific date, with the date format explicitly provided. This distinguishes it from sibling tools for stocks and crypto, and from forex_get_aggregate_bars which targets individual pairs.

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 phrase 'entire forex market' implies it is used for obtaining data across all forex pairs rather than a single symbol, but it does not explicitly name alternatives or state when not to use it. The usage context is implied but not fully articulated.

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