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

No annotations are provided, so the description must disclose behavioral traits. It implies a read-only, real-time quote retrieval, but does not state what data is returned, whether it returns a list or single quote, any rate limits, or how the 'short' parameter affects behavior. The phrase 'monitor changes in their performance' is vague and adds no concrete behavioral detail.

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 only two sentences, but it contains redundancy: 'real-time movements', 'live quotes', and 'monitor changes' all convey the same idea. The phrase 'with the FMP Stock Market Index Quotes API' is filler and not helpful. It is concise in length but not in content, with repeated concepts.

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 no annotations, the description should explain what the tool returns and how it behaves. It only says 'access live quotes' without specifying the format, scope, or relationship to the short parameter. The ambiguity with sibling getAllIndexQuotes makes this incomplete for a correctly selecting agent.

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 has 100% coverage for the single 'short' parameter, describing it as 'Whether to use short format'. The description adds no additional meaning or context about this parameter, such as how short format differs from full format. With full schema coverage, a baseline of 3 is appropriate, but the description does not enhance the schema.

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 the tool's purpose: to track real-time movements and access live quotes for stock market indexes. It uses specific action verbs ('track', 'access', 'monitor') and a specific resource ('major stock market indexes', 'global indexes'). However, it does not explicitly distinguish between this tool and closely related siblings like getAllIndexQuotes or getIndexQuote, though the plural 'Quotes' is a hint.

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 provided about when to use this tool versus alternatives such as getAllIndexQuotes, getIndexQuote, or getIndexShortQuote. The description only explains what the tool does, not the context or exclusions. Given the large sibling list, this is a significant gap.

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