getAllIndexQuotes

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

Annotations already indicate readOnlyHint, idempotentHint, and openWorldHint. The description adds that the data is 'real-time', which is somewhat at odds with idempotency (though not contradictory). It does not clarify data freshness, rate limits, or response size. Since annotations cover the safety profile, the description adds minimal extra behavioral context.

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 concise sentences: the first states the core purpose, the second adds context. Every word earns its place; no redundancy or filler.

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 a simple schema (one optional bool), no output schema, and good annotations, the description is mostly adequate. However, it does not mention the 'short' parameter or hint at the structure of the return value. For a tool with no output schema, this omission reduces completeness.

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 is fully described (100% coverage) with a single optional boolean 'short' parameter with a schema description. However, the tool description does not mention this parameter or explain its effect. At baseline 3, the description adds no further semantic value beyond what the schema already provides.

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 provides real-time quotes for stock indexes and allows multiple indexes in one request. However, it does not distinguish itself from sibling tools like getIndexQuotes (which may also return multiple indexes). The word 'All' in the name suggests a broad scope, but the description fails to specify what 'all' entails compared to getIndexQuotes.

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 no guidance on when to use this tool versus alternatives. It does not mention scenarios, prerequisites, or when not to use it. Given the presence of siblings like getIndexQuote (single index) and getIndexQuotes, the lack of usage guidance is a notable gap.

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