Get Detailed Quote

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

Annotations already declare readOnlyHint=true, so the description doesn't need to reiterate safety. It adds value by detailing the return fields (OHLC, change, volume, 52-week range, market status) and notes the tool is more detailed than get_price. No contradictions or additional behavioral issues mentioned.

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 concise yet comprehensive: a brief summary, bullet points for args and returns, and two examples. Information is front-loaded and every sentence adds value.

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 only 2 parameters, no output schema, and strong annotations, the description fully covers tool behavior, usage, and output. It explains when to use, what parameters are, and what the return data contains, making it easy for an agent to invoke correctly.

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 coverage is 100%, so baseline is 3. The description adds concrete examples for symbol (e.g., 'XAU/USD') and clarifies the meaning of response_format options ('markdown' for human-readable). This extra context merits a 4.

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 explicitly states 'Get comprehensive quote data including OHLC, change, volume, and 52-week range.' It uses a specific verb and resource, and immediately distinguishes from sibling 'get_price' by noting it is more detailed.

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 provides clear context for when to use this tool versus alternatives by saying 'More detailed than get_price' and includes example queries that demonstrate proper symbol formatting. It lacks explicit when-not-to-use guidance, but the differentiation is sufficient.

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