get_quote

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds valuable context beyond annotations by specifying the data source ('Continuum feed'), the live nature of prices, and the tool's purpose for pre-trade checks or monitoring, enhancing behavioral understanding without contradiction.

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 front-loaded with the core purpose in the first sentence, followed by usage guidelines in the second. Both sentences earn their place by adding distinct value—no wasted words, making it highly efficient and well-structured.

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 tool's low complexity (1 parameter, 100% schema coverage, annotations provided, no output schema), the description is mostly complete. It covers purpose, usage, and data source, but could slightly improve by hinting at return format or limitations, though annotations handle safety aspects adequately.

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%, with the schema fully documenting the 'symbols' parameter as an array of strings with min/max items. The description adds minimal semantics by implying symbol examples like 'EURUSD' and 'XAUUSD', but doesn't provide additional details beyond the schema, meeting the baseline for high coverage.

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 specific action ('Get the current live bid/ask price'), identifies the resource ('for one or more symbols'), and distinguishes it from siblings by specifying it returns prices from the Continuum feed for price checking or monitoring, unlike trading or account management tools in the sibling list.

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 explicitly states when to use this tool ('to check prices before trading or to monitor price levels'), providing clear context for its application. It distinguishes from siblings by focusing on real-time price data rather than order execution or account queries.

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