stock_prices

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

With no annotations, the description fully explains the return structure (envelope dict with fields and not_found list) and input constraints. It implicitly indicates a read-only operation but does not mention rate limits or caching behavior.

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 concise with a one-sentence summary followed by structured Args and Returns sections. Every sentence adds value without redundancy, and the key information is front-loaded.

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 the simple single-parameter input and absence of an output schema, the description covers all essential aspects: input format, constraints, return fields, and error handling via 'not_found' list. No critical gaps remain.

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 single parameter 'tickers' has 0% schema description coverage, but the tool description provides extensive semantics: comma-separated exchange-prefixed symbols, maximum 2000 items, and an example. This fully compensates for the missing schema documentation.

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 tool provides 'Current price + daily % change for specific stock symbols', with specific input format and output structure. It distinguishes itself from siblings by focusing on real-time price data rather than analysis or scanning.

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 specifies the required ticker format (exchange:SYMBOL), maximum batch size (2000), and example usage. However, it does not explicitly state when to use this tool versus alternatives like 'yahoo_price' or 'stock_extended_hours'.

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