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

With no annotations, the description carries the full burden. It mentions 'real-time' and 'key data' but fails to disclose that it is a bulk read (no symbol parameter) or what the 'short' format affects. This leaves important behavioral traits unexplained.

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 at two sentences and front-loaded with the core action. The second sentence is somewhat generic but not wasteful, earning its place by hinting at the data included.

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?

Despite a simple schema, the description is incomplete. It doesn't clarify whether quotes are returned for all ETFs or a selectable list, lacks any output structure info, and fails to connect to symbol-based siblings. The absence of a symbol parameter is a critical context gap.

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% for the single 'short' parameter, so the baseline is 3. The tool description adds no extra meaning beyond the schema, merely repeating that it tracks prices and performance.

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 it gets real-time price quotes for ETFs, using a specific verb and resource. The ETF scope distinguishes it from sibling quote tools like getQuote, getIndexQuote, and getMutualFundQuotes.

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?

No guidance is given on when to use this tool versus alternatives. The input schema has no symbol parameter, yet the description doesn't clarify that this returns quotes for multiple ETFs without filtering by symbol, which could lead an agent to misuse it for a specific ETF quote.

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