getIndexQuotes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the words 'real-time' and 'live', without clarifying freshness/latency, whether it returns one index or the whole set, or how it differs from the plural 'all' sibling — which is the behavior an agent most needs to know here.

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?

Two short sentences with the resource front-loaded, so it is not bloated. But 'monitor changes in their performance' is filler that restates 'track real-time movements', and the space would be better spent distinguishing this from its near-identical siblings.

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?

With no output schema and a single optional parameter, the description carries the burden of explaining what actually comes back (one index? all indexes? which fields?) and it does not. The unresolved overlap with getIndexQuote, getIndexShortQuote, and getAllIndexQuotes leaves a genuine selection 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% with a single optional boolean ('short' = use short format), so the schema already documents the only parameter. The description does not mention the short/long output toggle at all, but with full schema coverage the baseline of 3 applies.

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 states a verb and resource ('Track real-time movements of major stock market indexes', 'Access live quotes for global indexes'), so the general domain is clear. However, it reads like API marketing copy and never resolves the central ambiguity: the plural name sits alongside siblings getIndexQuote, getIndexShortQuote, and getAllIndexQuotes, yet the description gives no basis for telling them apart.

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?

There is no when-to-use guidance at all — no mention of which sibling to pick for a single index versus all indexes, no prerequisite or input requirement (e.g. that no index symbol is supplied), and no exclusion. An agent must guess between this tool and getAllIndexQuotes or getIndexQuote.

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