option_sse_minute_sina

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds the key behavioral trait of data being limited to the current trading day and specifies the return type (pandas.DataFrame), which complements the annotations without contradicting them.

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 compact and front-loaded with the main purpose and limitation. It includes a source URL and docstring-style parameter/return info, with no unnecessary 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?

The tool is simple with one parameter, and the description explains the return type and scope. However, it does not detail DataFrame columns or error behavior, which slightly reduces completeness for a tool without an output schema.

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 one optional parameter with no description. The description defines symbol as '期权代码' (option code) with type str, providing essential meaning. With schema coverage at 0%, this compensation is valuable, though it lacks examples or format details.

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 retrieves minute data for a specified option on the current trading day, explicitly noting historical data is unavailable. This distinguishes it from sibling tools like option_sse_daily_sina (daily data) and option_sse_spot_price_sina (spot price).

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?

It explicitly states a limitation ('只能获取当前交易日的数据, 不能获取历史分钟数据'), telling the agent not to use it for historical data. However, it does not name alternative tools for historical minute data, so it lacks explicit alternatives.

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