get_quote

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

No annotations are provided, so the description must carry full behavioral disclosure. It mentions 'live/delayed' but fails to disclose rate limits, authentication needs, error handling for invalid symbols, or whether the data is real-time or delayed by default. This is insufficient for a tool with no annotation support.

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, using bullet points for examples and avoiding unnecessary words. Every sentence provides useful information, and the structure is front-loaded with the core purpose.

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 simple tool with one parameter and no output schema, the description covers the main function and input formatting. It lacks error handling details or performance notes, but overall it is adequately complete for typical usage.

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% with a single parameter. The description adds substantial value by providing concrete symbol examples and format rules (e.g., .NS suffix for NSE, ^ for indices), which helps the agent construct valid inputs beyond the schema's generic description.

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 live/delayed stock quotes for any symbol worldwide. It lists examples for US stocks, NSE India, BSE India, and indices, effectively distinguishing from sibling tools like get_bse_quote and get_nse_quote.

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 implies this tool is for general quotes via examples, but it does not explicitly state when to use this versus siblings like get_crypto_quote or get_forex. No exclusions or alternative guidance is provided, leaving the agent to infer usage context.

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