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

With no annotations provided, the description carries the burden of disclosure. It adds context about real-time data, short-form fields, and batch processing, which is useful. It also lists expected output fields (price, change, volume). While it doesn't mention response format or limitations, it is not misleading and provides reasonable transparency for a read-only quote tool.

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 sentences, front-loaded with the core action and purpose. No redundant or extraneous information. The structure is clean and immediately comprehensible.

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?

For a simple one-parameter tool with no output schema, the description provides sufficient context: it explains the batch quote nature, the short-form data, and example output fields. It could be more explicit about the response format, but the tool is straightforward and the description covers the essentials adequately.

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 single parameter 'symbols' is fully described in the schema with 100% coverage as a comma-separated list. The description adds no new syntax or formatting details beyond the schema, only reinforcing the 'multiple' aspect. The schema already handles the semantics, so the description provides marginal additional value.

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 accesses real-time, short-form quotes for multiple stocks, specifying the FMP Stock Batch Quote Short API. It mentions key data like price, change, and volume, which distinguishes it from single-stock quote tools like getQuoteShort and full batch tools like getBatchQuotes.

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 implies usage for quickly fetching a snapshot of multiple stocks in one request, but it does not explicitly compare to alternatives or state when not to use this tool. The context of 'short-form' and 'multiple' is present, but no exclusions or alternative tools are named.

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