getSpreadTickers

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

With no annotations, the description discloses latency during high volatility and no authentication required. It also notes the return format (list with one ticker object). Minor omission: no mention of rate limits.

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, sections, and front-loaded purpose. Each sentence adds value, no redundant or unclear phrasing. Appropriate length (around 150 words).

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?

Covers purpose, usage guidelines, parameter details, latency, authentication, return format, and alternatives. Complete for a simple read tool with no output schema.

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 provides no description for the 'symbol' parameter (0% coverage). The description adds meaning by stating it's required and advising to use getSpreadInstrumentsInfo to obtain valid symbols, compensating well.

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 latest price snapshot, best bid/ask, and 24h stats for a spread symbol. It distinguishes from sibling tools like getSpreadOrderbook (depth) and getSpreadRecentTrades (trades).

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 states when to use (current price, 24h stats, best bid/ask) and when not to use (order book depth, recent trades) along with alternative tool names. Also provides agent hint and guidance on obtaining valid symbols.

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