get_candles

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only lists parameters and return fields, but does not indicate whether the tool is read-only, requires authentication, has rate limits, or any side effects. This is a significant gap for a data retrieval tool.

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 well-structured with 'Args' and 'Returns' sections, making it easy to scan. The purpose statement is front-loaded. While it could be slightly more concise, it is clear and effective.

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 tool has 5 parameters (1 required) and an output schema exists (though not shown). The description covers all parameters and returns, but lacks usage guidance and behavioral context. It is adequate for a simple data retrieval tool but not fully complete.

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%, so the description must compensate. It adds meaning by explaining each parameter with examples (e.g., 'symbol: Trading pair symbol (e.g., BTCUSDT, ETHUSDT)'), enumerating intervals, and specifying limit range/default. This adds significant value beyond the bare schema.

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 tool's purpose: 'Get OHLCV candlestick data for a cryptocurrency.' The verb 'Get' and resource 'OHLCV candlestick data' are specific and unambiguous. It distinguishes well from sibling tools, which are mostly technical indicators (e.g., get_sma, get_rsi) rather than raw price data.

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 provides no guidance on when to use this tool versus alternatives. It does not specify when not to use it or mention any preconditions. Given the many sibling tools, explicit guidance would be valuable but is absent.

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