xRocket 24h tickers

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds some useful context ('public', '24-hour', optional symbols), but it does not disclose potentially important behaviors such as whether omitting symbols returns the entire market or how repeated symbol queries behave.

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 a single clear sentence that front-loads the core purpose and then adds the optional symbols detail. There is no filler or redundant restatement of the title.

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?

The schema, annotations, and output schema are fairly rich and reduce the need for return-format details, so the description is close to sufficient. However, given that symbols is optional, the agent would benefit from knowing whether omitting it returns all available tickers and what 'repeated list of symbols' means operationally. This is a real gap for correct invocation.

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?

There is one parameter, and the schema item description already documents exact symbol formatting with an example. The description adds that the symbol list is optional, but it does not meaningfully explain filtering behavior, default behavior when the parameter is absent, or the repeated-list concept that the description references.

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 identifies the operation ('Get public 24-hour ticker data') and the resource scope ('24-hour tickers'), which distinguishes it from sibling tools like orderbook, candles, trades, or rates. The optional symbols list is also mentioned, so the purpose is immediately understandable.

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?

The description states what the tool gets but gives no guidance on when to choose it over sibling tools such as xrocket_market_snapshot, xrocket_market_candles, or xrocket_market_orderbook. There is also no mention of what happens when the optional symbols parameter is omitted, which would help the agent decide whether to supply it.

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