getBatchAftermarketTrade

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

The description adds context about real-time data and the specific data points (prices, volumes, timestamps), but annotations already declare readOnlyHint, idempotentHint, and openWorldHint. There is no contradiction, and the description does not disclose additional behavioral traits like rate limits or pagination.

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 two sentences, front-loaded with the main purpose, and elaborates on tracked data. Every sentence adds value without redundancy.

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?

Given no output schema, the description hints at response fields (prices, volumes, timestamps). It is fairly complete for a simple one-parameter tool, though it could be improved by mentioning that the response is an array of objects.

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 covers 100% of the single parameter 'symbols' with a description. The description confirms it's for multiple stocks but does not add extra semantics like format constraints or maximum count. Baseline 3 is appropriate as schema does the heavy lifting.

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 verb 'Retrieve' and the resource 'real-time aftermarket trading data for multiple stocks'. It specifies the data type (trade prices, volumes, timestamps) and explicitly mentions 'multiple stocks' which distinguishes it from sibling single-stock tools like getAftermarketTrade.

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 explains what the tool does but does not provide explicit guidance on when to use it versus alternatives. It implies batch usage but does not mention cases where one would prefer getAftermarketTrade for a single stock or getBatchAftermarketQuote for quotes.

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