getStocks

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

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds rate limit group and confirms the endpoint, but lacks details on response format, error handling, or behavior for invalid symbols. The information provided is adequate 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?

Description is concise: title, bullet-like list of returned fields, rate limit group, and HTTP method. Each sentence adds value, and the structure is front-loaded with the most important info. No unnecessary words.

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?

The tool is simple with one parameter, but the lack of an output schema leaves the response format unknown. The description mentions some fields (name, market, currency) but not all, which may require the agent to infer or call the tool to discover the structure. Error scenarios are not covered.

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?

Schema coverage is 100%, so the baseline is 3. Description repeats the symbols parameter's bulk limit (200) but does not add new semantics beyond the schema's own detailed description. No additional constraints or clarifications are introduced.

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 it retrieves basic stock info (name, market, currency, etc.) and supports bulk query of up to 200 symbols. It distinguishes the tool's purpose from price or order tools implicitly, but does not explicitly differentiate from siblings like getStockWarnings or getPrices.

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?

No guidance on when to use this tool vs alternatives such as getPrices or getCandles. The description only explains what it does, not when it should be preferred or when other tools are more appropriate.

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