crypto_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 fully disclose behavior. It only says 'Get daily OHLC', implying a read operation but does not disclose return format, pagination, timezone handling, adjustment behavior, or data availability. The adjusted parameter is not explained, and no output schema exists to fill the gap.

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 concise sentence with no filler. Every word adds meaning, and the key date format is front-loaded.

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 simple tool with no output schema and no annotations, the description covers the core purpose but lacks important behavioral details like what the response contains (e.g., array of bars), how 'adjusted' affects results, or whether the data includes all crypto assets. The absence of any mention of the adjusted parameter is a notable gap.

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 description adds format details for the date parameter (YYYY-MM-DD), which is useful since schema has no descriptions. However, the adjusted parameter is completely omitted, leaving the agent to guess its meaning or rely on external knowledge. Partial coverage, so a mid-score 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?

The description clearly states the action ('Get daily OHLC'), the resource ('entire crypto market'), and the key parameter (date with format). This distinguishes it from per-ticker tools or other market data tools like crypto_get_aggregate_bars or crypto_get_snapshot.

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 on when to use this tool versus alternatives. It does not mention that for single-ticker data one should use crypto_get_aggregate_bars, or that other grouped_daily_bars tools exist for stocks/forex. The implicit context is not enough for an agent to choose correctly among many sibling tools.

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