get_bulk_candles

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

With no annotations, the description carries the transparency burden. It discloses a key behavioral trait: 'Sends a command to EA and waits for the result (up to 120 seconds)', which is valuable for understanding latency and side effects. It also mentions the return of candle data, but lacks details on error handling or read-only nature.

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 three sentences, front-loaded with the main purpose. The Korean repetition duplicates content but is concise overall and does not contain unnecessary filler.

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 description explains the command-wait mechanism and states that it returns candle data for all requested timeframes. Since there is no output schema, this satisfies the need for return information. It is complete enough for the tool's complexity, though it omits potential error details.

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 100% with each property described in the schema. The tool description does not add extra parameter semantics beyond what the schema already provides, so the baseline score of 3 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 'Get historical candle data for multiple timeframes at once' with a specific verb and resource. It distinguishes itself from the sibling tool 'get_candles' by emphasizing the multi-timeframe capability.

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 implies when to use this tool ('for multiple timeframes at once') without explicit exclusions or alternatives. It provides clear context but doesn't explicitly say 'use this instead of get_candles when you need multiple timeframes'.

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