stock_prices

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

Annotations already mark it as read-only and non-destructive. Description adds significant behavioral context: one upstream request even for full 2000 tickers, exchange-scoped lookup, and return structure including a not_found list. No rate limits mentioned, but overall transparent.

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?

Description is well-structured with Args and Returns sections, providing necessary information in a compact form. No redundant sentences; every part adds value. Efficient for an AI agent to parse.

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?

Despite no output schema, the description details the return envelope including fields like ticker, symbol, price, change_percent, and not_found list. Covers input format, limits, and behavior. Could mention rate limits or auth requirements, but overall complete for a read-only data fetch tool.

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?

With 0% schema description coverage, the description fully defines the single parameter 'tickers': comma-separated EXCHANGE:SYMBOL list, max 2000, with required exchange prefix. Provides examples and clarifies behavior. Exceeds the schema's minimal definition.

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?

Description clearly states 'Current price + daily % change for specific stock symbols' and specifies the required ticker format with exchange prefix. It distinguishes itself from sibling tools like top_gainers and yahoo_price by focusing on fetching raw price data for user-specified symbols with a specific input format.

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?

Description implies when to use: to get prices for specific stocks by symbol. It explains the format 'EXCHANGE:SYMBOL' and max 2000 tickers. However, it does not explicitly compare with alternatives like yahoo_price or market_snapshot, but the emphasis on exchange-scoped lookup provides enough context.

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