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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful return-content semantics (bid, ask, daily percent change) but says nothing about snapshot timing, delayed vs real-time data, behavior for invalid symbols, or market-closed states — all material for a live-quote 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?

One sentence, zero filler, and the most decision-relevant information (what data, which markets) is front-loaded. Nothing is repeated from the schema or annotations.

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 one-optional-parameter, no-output-schema read tool, the description does the needed work by naming the returned fields and the asset universe. The remaining gap is timing/freshness semantics, which matter for a tool titled 'Live quotes' but are left unstated.

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 description coverage is 100% and the single optional 'symbols' parameter is documented in-schema with format example and the 'omit for all' default. The description adds only indirect value by listing which instrument classes are supported, which implicitly bounds valid symbol values; baseline 3 applies.

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?

States a specific resource (bid/ask and daily % change) and enumerates the covered asset classes (forex majors/minors, metals, oil, crypto), so an agent knows exactly what data comes back. It stops short of naming how it differs from siblings such as get_currency_strength or get_screener, which could read as adjacent price-data tools.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the sibling list whether a live quote request belongs here or in get_currency_strength. The only routing hint, 'Omit for all', lives in the schema rather than the description.

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