get_rates

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

No annotations provided. Description only mentions output format (OHLCV bars) but no behavioral traits like rate limits, data depth, or side effects. With zero annotation coverage, description carries full burden but lacks detail.

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?

Single sentence, efficient, front-loaded with verb and resource. No redundant 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?

Missing parameter details for count and start_pos, no usage guidelines, and limited behavioral transparency. Output schema exists but does not compensate for the gaps in the description.

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?

Description only covers symbol and timeframe with examples, but fails to explain count and start_pos. Schema description coverage is 0%, so description must compensate, which it does not. Two parameters are left 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 clearly states the verb 'Get' and resource 'OHLCV bars' with parameters symbol and timeframe. It distinguishes from sibling tools which focus on analysis, orders, and account info.

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?

Provides examples of timeframes but no explicit when-to-use vs alternatives, no when-not or exclusions. Context implies basic data retrieval, but more guidance would help.

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