get_us_multi_price

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

No annotations exist. The description only mentions 'snapshot' and does not disclose data freshness, whether it returns last price only, rate limits, or error handling. Behavioral traits beyond basic function are minimal.

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 short, front-loaded with purpose, and structured with Args. The mix of English and Korean might be slightly verbose but does not detract from clarity.

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 an output schema exists, the description need not explain return values. The description covers usage and parameter constraints adequately for a simple batch price tool, but lacks details on error handling or data fields.

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 description adds that tickers should be a list of tickers with max 20 recommended, which fills a gap since schema coverage is 0%. However, it does not specify format (e.g., symbol only) or that they are US tickers specifically.

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 is for US multi-ticker prices (snapshots) with example queries. The verb and resource are specific. It does not directly differentiate from siblings like get_price or get_us_price, but the name and context imply batch querying.

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?

Example queries are provided, implicitly showing use cases. A max recommendation of 20 tickers is given. However, no explicit guidance on when not to use or alternatives is included.

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