get_multi_chart_stats

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

With no annotations, description handles transparency well by noting parallel bulk query, aggregate-only return. Could add details on error handling or rate limits but sufficient for a read tool.

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?

Well-structured with bold key points, bullet args, and caution emoji. Slightly verbose in places but mostly efficient for a tool with 2 params.

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 output schema exists (not shown), description needn't detail return format. It lists returned fields and provides usage context. Adequate for a bulk stats tool.

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 has 0% coverage, but description explains both params: codes (list of stock codes, max 100) and days (lookback period, default 260 days). Adds practical meaning beyond 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?

Description clearly states it returns aggregate statistics (current/high/low, drawdown, period return) for multiple stocks in parallel. Distinguishes from sibling 'get_chart' which returns time series candles/OHLCV.

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 when to use (bulk aggregate queries instead of multiple get_chart calls) and for screening (e.g., drawdown filter). Also warns 'not time series' to avoid misuse.

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