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

With no annotations, the description must convey the tool's behavioral profile. It discloses the returned data (price, % change, 52-week high/low, exchange, currency) but omits potential error behavior, rate limits, or data source reliability. For a read-only quote tool, this is adequate but not comprehensive.

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 highly concise, consisting of two sentences that immediately state the core function and return fields. There is no filler 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?

Given the tool's simplicity, the absence of an output schema, and the description's listing of return fields, it provides sufficient context. It could be more explicit about the response structure (e.g., array of objects) or handling of multiple symbols, but it is reasonably complete for a quote retrieval tool.

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?

The input schema already provides full descriptions and defaults for both parameters (100% coverage). The description adds little beyond confirming that one or more symbols are supported, which aligns with the 'symbols' parameter. No deeper parameter semantics are provided.

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 ('Get') and clearly identifies the resource ('real-time stock price quotes') for one or more symbols. It also lists return fields, which distinguishes it from sibling tools for holdings and indices.

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 implies when to use the tool: whenever real-time stock quotes are needed. However, it doesn't explicitly mention alternatives or exclusions, though the sibling tool names make the differentiation obvious.

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