getAftermarketQuote

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 that data is real-time and scoped to the aftermarket session, but says nothing about freshness/latency guarantees, empty results outside extended hours, or subscription prerequisites for the API.

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 compact sentences with the resource stated first. The trailing 'and other relevant data' and the 'with the FMP Aftermarket Quote API' brand mention are slightly padded but not obstructive.

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 read-only quote lookup with full schema coverage and annotations, the description covers what the tool returns and when the data applies. A brief pointer to the batch variant or regular-hours quote sibling would have made it complete.

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?

There is a single required parameter 'symbol' with 100% schema description coverage, so the schema already carries the documentation burden. The description adds no format guidance (e.g., exchange suffix conventions, case handling), which is the baseline expectation when schema coverage is high.

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 names a specific resource — real-time aftermarket quotes for stocks — and lists the data points returned (bid, ask, volume). The phrase 'outside of regular trading hours' implicitly distinguishes it from the regular-hours sibling getQuote, though it never names that sibling or getAftermarketTrade explicitly.

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 context is only implied via 'outside of regular trading hours'; there is no explicit statement of when to pick this over getQuote, getQuoteShort, getAftermarketTrade, or getBatchAftermarketQuote. An agent must infer the selection rule from the tool name and the time-of-day phrasing.

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