getIndexPriceComponents

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

Annotations already mark read-only and open-world. The description adds that no authentication is required, specifies the returned fields (indexName, lastPrice, updateTime, components), and discloses a scope limitation (not available for xStock tokens like TSLAXUSDT). No contradictions with annotations.

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 main body is well-front-loaded with a clear first sentence and use-case bullets, but the Agent hint section overlaps heavily with earlier text, repeating the purpose, the getTickers exclusion, and return summary. The extra TradFi example is valuable, but the redundancy makes it slightly less concise.

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?

For a single-parameter read-only endpoint with no output schema, the description is remarkably complete: it covers input format, return fields, use cases, exclusions, auth requirements, and asset-class applicability. An agent can invoke correctly without additional lookups.

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 zero description coverage and a single primitive indexName parameter. The description compensates with required status, concrete examples (BTCUSDT, ETHUSDT), special-case values (XAUUSDT, XAGUSDT, CLUSDT), and a warning against unsupported inputs (TSLAXUSDT).

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 opening sentence uses a specific verb ('Retrieve') and names the resource (component exchanges and trading pairs of a Bybit index price) with their weights, prices, and multipliers. It differentiates from siblings by explicitly noting it is not the tool for index price alone, pointing to getTickers.

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?

Lists concrete use cases (understand contributions, investigate why an index differs, research methodology) and an explicit exclusion ('Do not use this endpoint for the index price value alone — use getTickers'). TradFi-specific examples further guide correct selection for commodity versus stock tokens.

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