get_multi_stocks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful constraints: max 30 codes, and token efficiency. It doesn't describe error handling or partial-result behavior, but given the annotations, this is adequate.

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 slightly verbose but every sentence earns its place: purpose, usage examples, efficiency note, and parameter details. It is front-loaded with the core function and uses a clean Args block. Could be tightened, but it is well-structured.

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?

An output schema exists, so return format is covered. The description covers when to use, the parameter meaning, and a constraint. It doesn't explicitly state this is for Korean stocks, but that is implied by the code format and the sibling get_us_multi_price. Missing minor edge cases, but overall sufficient.

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 has 0% coverage for the parameter description, but the description explicitly defines 'codes' as a list of Korean stock codes, sets a maximum of 30, and gives concrete examples (e.g., ['005930', ...]). This fully compensates for the schema gap.

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 states a clear verb ('fetches basic info for multiple stocks at once') and specifies the exact data fields (price, change rate, volume). It also differentiates itself from the sibling get_price by explicitly framing itself as the bulk alternative, so an agent can immediately tell it apart.

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 explicit usage examples ('Show me current prices for these stocks'), names the alternative (get_price) and the condition for choosing this tool (multiple vs individual calls), and even highlights token efficiency. It also calls out a specific scenario (comparing N screening results). This is complete guidance.

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