getMarketKline

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

With no annotations, description fully discloses behavioral traits: data returned in reverse chronological order, up to 1000 records per request, no authentication required, and the 7-element array format. Provides comprehensive transparency beyond what annotations would typically convey.

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?

Well-structured with sections and bullet points, but slightly redundant (reverse chronological mentioned twice). Still concise for the information provided, with front-loaded key purpose.

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?

Given 6 parameters, no output schema, and no annotations, the description covers purpose, usage, data format, limitations, and alternatives thoroughly. It provides enough context for an agent to invoke the tool correctly without additional information.

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 0%, but description adds context: start/end timestamps in milliseconds, supported categories (spot, linear, inverse), and limit max 1000. While not detailing every parameter, it compensates with useful semantics that the schema lacks, though slightly verbose.

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 explicitly states it queries historical klines (OHLCV candlestick data) and lists the fields. It distinguishes from sibling tools by stating 'Do not use this endpoint for mark price candles — use getMarkPriceKline instead' and similarly for index price, clarifying its specific resource and scope.

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 explicit when-to-use scenarios: building price charts, technical analysis, data for time range. Also gives clear when-not-to-use with named alternative tools (getMarkPriceKline, getIndexPriceKline, getPremiumIndexPriceKline), offering strong guidance for tool selection.

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