getMarkPriceKline

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

Discloses no authentication required, data order (reverse chronological), and data format (5-element array). Lacks details on rate limits or error handling, but overall transparent for a read-only query.

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 bullet points and clear sections, but slightly redundant (reverse chronological mentioned twice). Front-loaded main purpose. A bit lengthy but justified by complexity.

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?

Adequately explains tool purpose and relationship to siblings, but lacks parameter semantics despite 0% schema coverage. Missing details on parameter formats and pagination. Output schema not provided, but description partially compensates with data format.

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 has 0% description coverage. Description does not explain parameters (category, symbol, interval, start, end, limit) beyond what is in the schema. Only mentions interval implicitly via enum list. Agent hint is generic. Needs explicit parameter descriptions.

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 'Query historical mark price klines used for margin and liquidation calculations' and distinguishes from siblings: 'Do not use this endpoint for regular trading price candles — use getMarketKline instead. Do not use this endpoint for index price candles — use getIndexPriceKline instead.'

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?

Explicitly lists use cases (risk management, charting) and provides clear exclusions with alternatives, including supported products (USDT contract, USDC contract, Inverse contract).

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