getBatchAftermarketQuote

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds the post-market scope and enumerates the payload fields (bid, ask, volume), which is useful but thin. Nothing is said about rate limits, batching size limits, or behavior for invalid symbols.

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 action and resource. Minor waste in the vendor-branded phrase "with the FMP Batch Aftermarket Quote API" and the vague "other relevant data," but nothing materially distracting.

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 one-parameter batch quote read with no output schema, the description covers the domain (post-market), the multi-symbol scope, and the kind of values returned. An agent has enough to call it correctly; only edge-case behavior is unaddressed.

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 coverage is 100% with a single required parameter, and the schema already documents "Comma-separated list of stock symbols." The description adds no format, limit, or normalization detail beyond that, so 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?

States a specific verb and resource: "Retrieve real-time aftermarket quotes for multiple stocks." The word "multiple" plus "batch" distinguishes it from the single-symbol getAftermarketQuote and from regular-hours getBatchQuotes listed among its siblings. It stops short of naming those siblings outright.

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?

Usage is only implied by the phrase "during post-market trading," which tells the agent this is not a regular-session quote tool. There is no explicit statement of when to prefer it over getAftermarketQuote (single symbol) or getBatchQuotes (regular hours), and no prerequisites or exclusions are given.

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