getAftermarketQuote

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

Annotations (readOnlyHint, idempotentHint) already indicate safe read-only behavior. Description adds that it provides bid/ask prices, volume, and 'other relevant data', giving useful detail about returned fields beyond annotations.

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, direct sentences with no filler. Front-loads the purpose and key details efficiently.

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 single-parameter tool without output schema, the description is sufficient to understand functionality and basic results. Missing details like error handling or market-hour constraints, but adequate for typical use.

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 describes 'symbol' generically as 'Stock symbol'. Description specifies the tool is for stocks, adding context beyond the schema. With 100% schema coverage, baseline is 3, but description elevates to 4.

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?

Clearly states 'Access real-time aftermarket quotes for stocks', specifying verb (access), resource (aftermarket quotes), and scope (stocks). Distinguishes from sibling tools like getAftermarketTrade or getQuote.

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?

Implies use for aftermarket hours but provides no explicit guidance on when to use vs. alternatives (e.g., getQuote). No exclusions or context for when not to use this tool.

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