get_us_multi_price

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

Annotations already include readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false, so the safety profile is clear. The description adds a practical recommendation (max 20 tickers) and clarifies it's a snapshot, but does not mention rate limits or error behavior beyond that.

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 clear title, examples, and a parameter block. It front-loads the purpose and usage examples, though the Korean repetition could be trimmed without losing value.

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?

With a simple 1-parameter schema, an output schema present, and annotations covering safety, the description is largely sufficient. It could add a note on the maximum number of supported tickers (there is only a 'recommended' limit) or expected output format, but these are minor gaps.

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 'tickers' as an array of strings with no description, and schema description coverage is 0%. The description provides a useful example and the max-20 guidance, which adds meaning beyond the bare schema, but it does not fully specify the expected format (e.g., uppercase, separator).

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 it fetches US multi-ticker prices in batch, distinguishing it from siblings like get_us_price (single ticker) and get_multi_stocks (generic multi-stock). The examples and Korean translation reinforce the purpose, but it does not explicitly name the distinguishing sibling.

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?

It provides concrete example queries that trigger usage and recommends a max of 20 tickers. It implies use for multi-ticker price snapshots, but does not explicitly say when NOT to use it (e.g., for detailed data, use get_us_info).

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