get_multiple_stock_prices

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

The description is straightforward for a read operation but doesn't disclose expected behavior like rate limits, response format, or data source. There are no annotations provided, so the description carries the full burden of behavioral disclosure, but 'real-time' hints at the nature of the data.

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 a single, efficient sentence that states purpose without waste. It is front-loaded with the verb and resource, followed by the scope qualifier 'multiple'.

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 tool with only one parameter, high schema coverage, and no output schema, the description is adequately complete. It covers what the tool does and the parameter semantics are clear from the schema.

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 schema provides 100% coverage with a clear description of the symbols parameter and a concrete example. The description doesn't add additional meaning beyond the schema, but the example in the schema is sufficient for correct parameter usage.

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 uses a specific verb ('get'), names the resource ('real-time stock price information'), and clearly distinguishes this from siblings like get_stock_price by emphasizing 'multiple' symbols. It establishes that this tool handles batch queries.

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 clearly implies this is for fetching price data for multiple symbols at once, distinguishing it from get_stock_price which handles a single symbol. However, it doesn't explicitly state when to prefer this over get_financial_data or other siblings.

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