get_multiple_tickers

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

No annotations are provided, so the description carries the burden. It discloses the batching behavior and the 50-symbol limit (though also present in the schema), but it does not describe error handling, return format, or side effects. Since 'get' implies a read-only operation, this 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?

The description is a single, efficient sentence that front-loads the action and resource. Every word earns its place with no superfluous information.

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 simple tool with one parameter and no output schema, the description provides sufficient operational context. It could be enhanced by mentioning the single-ticker sibling alternative, but the tool is straightforward enough that this omission does not create significant ambiguity.

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 defines the 'symbols' array with regex pattern and constraints, and the description does little beyond calling them 'symbols'. It ties the parameter to the tool's purpose but does not explain the symbol format or add meaningful detail beyond the schema, which has 0% coverage.

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 action ('Get ticker data'), the resource ('for multiple symbols'), and the batching nature ('at once'). It distinguishes from the sibling tool get_ticker by emphasizing 'multiple' and the 50-symbol limit.

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 phrase 'at once' implies batch retrieval for multiple symbols, which gives clear context for when to use it. However, it does not explicitly mention that for a single symbol one should use get_ticker, so no exclusions or alternatives are named.

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