queue_run

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the call drains the entire queue in parallel and returns final per-task status, but says nothing about blocking/long-running behavior, failure handling for individual tasks, or whether the operation is resumable or cancellable.

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 compact sentence with the action front-loaded and no filler. Every clause contributes: the drain-until-empty scope, the parallel execution mode, and the return value.

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?

There is no output schema and no annotations, so the description must compensate. It does state that per-task final statuses are returned, but omits error behavior, empty-queue behavior, and blocking characteristics for what is effectively a long-running batch operation.

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% and the single 'parallel' parameter is documented in the schema with its default of 2. The description's mention of '并行下载' corroborates that parameter but adds no syntax or semantics beyond it, so the baseline of 3 applies.

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?

States a specific verb and resource: consume the queue until it is empty, with parallel downloads, returning each task's final status. It clearly differs from siblings like queue_add, queue_list, queue_remove and queue_retry, though it never names them explicitly.

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 phrase 'consume the queue until empty' implies this is the execution trigger for a previously populated queue, but there is no explicit when-to-use guidance, no statement about interaction with queue_add or cancel_download, and no note on whether it should be called when the queue is already empty.

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