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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It mentions 'real-time' and 'track price changes and trading activity', which provides some transparency about the data freshness and contents. However, it does not clarify return format, pagination, rate limits, or other behavioral nuances, making this adequate but not thorough.

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 two sentences long and front-loaded with the core purpose. Every sentence adds relevant information: the first states what the tool retrieves, and the second clarifies the use case (tracking price changes and trading activity). No wasted words or redundant information.

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?

The tool is relatively simple with only two parameters and no output schema. The description provides enough context to understand the tool's scope and intended use. However, since there is no output schema, mentioning what fields are returned (e.g., price, volume, change) would improve completeness, though the phrase 'price changes and trading activity' partially covers this.

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 'exchange' described as 'Exchange name (e.g., NASDAQ, NYSE)' and 'short' as 'Whether to use short format'. The description adds no additional parameter-level detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses a specific verb ('Retrieve') and clearly identifies the resource: real-time stock quotes for all listed stocks on a specific exchange. It distinguishes itself from sibling tools like getQuote (single quote) and getBatchQuotes by emphasizing the exchange-wide scope.

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 clearly states the context for use ('all listed stocks on a specific exchange'), which implies it is meant for exchange-wide quote retrieval rather than individual or batch arbitrary symbols. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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