get_today_timeline

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe-read nature is known. The description adds only the data fields (price, volume, average) but no behavioral traits such as data availability delays, return format, or behavior on non-trading days. It does not contradict annotations.

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 a single, compact sentence that immediately states the purpose and data content. There is no filler, repeated information, or unnecessary detail.

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?

For a one-parameter, read-only tool with no output schema, the description covers the essential function and fields, but it lacks an explicit description of the response structure (e.g., array of minute-by-minute objects, timestamp fields). Some limitations (e.g., only trading days, real-time vs delayed data) are not mentioned, leaving gaps for an agent.

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 already provides a thorough description for the 'code' parameter with examples ('sz000001' or 'sh600000'), covering 100% of parameters. The tool description does not add additional parameter-level meaning beyond what the schema already states.

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 uses a specific verb '获取' (get) with a clear resource: 'A股当日分时走势数据' (A-share intraday trend data for the day). It further specifies content (每分钟的成交价、成交量、均价), and the '当日' scope distinguishes it from broader or historical tools like get_minute_kline or get_history_kline.

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 no guidance on when to use this tool versus alternatives. It does not mention when to prefer this over similar sibling tools like get_minute_kline or get_a_share_quotes, nor does it state any exclusions or prerequisites.

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