get_multi_stocks

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

No annotations provided, so the description carries full burden. It discloses the maximum of 30 codes and the read nature (fetching basic info), but doesn't explicitly state it is read-only or mention rate limits. Still, it provides actionable behavioral hints.

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 brief but dense: first sentence states function, followed by typical queries, efficiency note, and necessity. Parameter explanation is clear. No wasted 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?

Given the tool's simplicity (bulk fetch with one parameter) and the presence of an output schema, the description covers all needed aspects: usage, constraints, and value over alternatives.

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 description coverage is 0%, but the description fully explains the 'codes' parameter: it's a list of stock codes, max 30, with examples. This adds significant meaning beyond the bare schema.

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 tool fetches basic info (price, change, volume) for multiple stocks at once. It specifies the resource and distinguishes itself from repeated calls to get_price, making the purpose unambiguous.

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?

Explicitly advises use for bulk lookup and comparing screening results, and notes token efficiency over multiple get_price calls. Though it doesn't list when not to use, the context is strong enough for an AI agent to decide.

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