futures_daily_stats

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

No annotations are provided, and the description does not disclose behavioral traits beyond the basic functionality. It warns about data size but does not mention whether the operation is read-only, any side effects, or rate limits.

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 extremely concise with two sentences, front-loading the main purpose and adding a key warning. Every sentence serves a purpose without any 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?

With one parameter and no output schema, the description covers the essential purpose and a usage warning. However, it lacks specifics about the output fields beyond '涨跌幅、成交量等', leaving some ambiguity about what the returned data contains.

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 description adds meaning beyond the schema by warning about the consequences of not passing the symbol parameter (huge data). The schema already describes the parameter, but the description adds practical context.

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 verb '获取' (get) and the resource '期货24小时价格变动统计' (futures 24-hour price change statistics). It effectively conveys the tool's purpose, though it does not explicitly differentiate from similar sibling tools like futures_klines or futures_prices.

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 a warning about passing the symbol parameter to avoid huge data, which gives context on when to use the tool. However, it does not specify alternatives or when not to use this tool versus other tools.

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