dast_airline_operation_statistics

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

With no annotations, the description carries the transparency burden. It explicitly discloses that the tool returns a temporary xlsx download link valid for 24 hours and containing 5 sheets, and the verb '查询' signals a read-only operation. It omits auth/rate-limit details, but for a read-only statistics tool the output artifact and TTL disclosure are meaningful.

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 dense sentence that front-loads the purpose, then lists metrics, query dimensions, and the output artifact. It is compact and free of filler, though the metric list is somewhat run-on.

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 report-generation tool with no output schema, the description covers the essential contract: input dimensions, output artifact, validity period, and sheet count. It could name the five sheets or clarify empty-data behavior, but an agent has enough to invoke it and handle the result.

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 100%, so the schema already documents airline, start/end dates, and passenger type. The description only restates these as query dimensions without adding new semantic details, matching the baseline for fully covered schemas.

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 identifies the resource ('指定航司') and the operation ('统计周期内运行全貌'), enumerates the metrics, and states that it returns an xlsx download link. It does not explicitly name sibling alternatives, so it falls short of top marks, but the airline scope distinguishes it from dast_airport_operation_statistics.

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?

No when-to-use guidance, exclusions, or alternative tool references are provided. The phrase '按航司、开始日期、结束日期、运输类型查询' describes parameter usage, not when to choose this tool over siblings like dast_flight_overview_daily or dast_airport_operation_statistics.

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