cancel_download

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

With no annotations, the description carries the full burden. It does disclose one important behavioral trait — the task's breakpoint state is preserved and resumption is possible — but it omits what state the task ends in (cancelled vs removed from list_downloads), whether partial data remains, and whether the operation is immediate or requires permissions.

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?

A single sentence that front-loads the action and uses the parenthetical only for the semantically important qualifier. Nothing is wasted and nothing is buried.

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 mutation with no annotations and no output schema, the description covers the core action and its key side effect, but leaves the id's origin/semantics and the resulting task state unspecified — gaps an agent would have to resolve by trial or by reading siblings.

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 0% and the single 'id' parameter is undocumented in the schema. The description's reference to '一个下载任务' implies the id identifies a download task, adding marginal meaning, but it never confirms the identifier's source (e.g. from list_downloads or start_download) or accepted format.

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 states a specific verb+resource: cancelling a download task, with the parenthetical clarifying the scope (state is retained). It is distinguishable from start_download/download_status/wait_download by the cancel action, but it does not explicitly name any sibling or contrast itself with a delete-like alternative.

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 parenthetical '保留断点状态，可再次续传' implies when this is appropriate (stop now, resume later), which is useful inference, but there is no explicit when-to-use statement, no preconditions, and no named alternative for a non-resumable stop.

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