stock-price-multi

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

With no annotations provided, the description carries the full burden. It discloses the data source (Yahoo Finance) and that no API key is needed, and lists the return fields. However, it doesn't mention rate limits, update frequency, error handling for invalid tickers, or any destructive behavior (none expected). Basic but not comprehensive.

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 concise paragraph that front-loads the core purpose and then lists returned fields and data source. Every sentence adds value. Could be slightly more structured but is efficient.

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 tool's simplicity (one parameter, no output schema), the description covers the essential context: purpose, input constraints, output details, and data source. The only missing element is error handling information, but overall it's sufficient for an agent to select and invoke the tool correctly.

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 covers 100% of the single parameter 'tickers' with a description. The tool description reinforces the limit of up to 5 tickers and provides example symbols, adding marginal value beyond the schema. No additional semantic details (e.g., format requirements) are needed.

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 returns current US equity prices for up to 5 tickers and specifies the output fields (price, change %, volume, day range, 52-week range). It differentiates from siblings like 'us-stock-price' by emphasizing the multi-ticker capability, but doesn't explicitly name alternative tools.

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 provides clear context on when to use this tool: to get prices for multiple US stock tickers in one call, noting it is cost-effective ($0.025 per call) and sourced from Yahoo Finance with no API key. However, it lacks explicit when-not-to-use instructions or comparisons to specific sibling tools.

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