Candlesticks

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

Annotations already declare readOnly and idempotent; description adds defaults, maximum count, and allowed enum values, matching annotations. No contradiction; discloses key behavioral traits like parameter defaults and limits.

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?

Two sentences plus a listing of values; front-loaded with purpose, then defaults. No wasted words, efficient for quick parsing.

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?

Covers input parameters well but lacks description of output structure (OHLCV fields, format). Since no output schema exists, description should clarify return format; current absence leaves agents uncertain about response shape.

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 100%, and description summarizes defaults and constraints, adding value by compactly listing allowed period and trade_sessions values, which helps agents quickly interpret parameter options.

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?

Clearly states verb (Get) and resource (candlestick data (OHLCV)). Includes defaults and allowed values for parameters, distinguishing it from siblings by focusing on simple retrieval without date range flexibility.

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?

Indicates when to use (candlestick data) but does not explicitly exclude alternatives like history_candlesticks_by_date or by_offset when custom date ranges are needed. No mention of prerequisites or when not to use.

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