getIndexPriceComponents

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

No annotations exist, so the description is the only source of behavioral info. It states no authentication required and hints at supported indices. While it could mention rate limits or pagination, it adequately covers the read-only nature and scope for a straightforward 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-organized with bullet points, sections, and a clear agent hint. Every sentence adds value without redundancy, making it concise and easy to parse.

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 the single parameter and no output schema, the description adequately explains return fields (indexName, lastPrice, updateTime, components array). It covers basic usage and examples, though it could mention error scenarios or edge cases for completeness.

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 the description compensates by explaining the sole parameter indexName with examples (BTCUSDT, ETHUSDT, XAUUSDT, etc.) and constraints (not available for xStock tokens), adding significant semantic value beyond the 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 retrieves component exchanges and trading pairs making up a Bybit index price, including weights, current prices, and multipliers. It distinguishes from the sibling tool getTickers by specifying that this tool provides composition details, not just the index price.

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 (understand contributions, investigate price differences, research composition) and a clear when-not-to-use (for index price alone, use getTickers). Includes examples like BTCUSDT, ETHUSDT, and TradFi commodities, with notes on unsupported tokens.

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