douyin_queue_cancel

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

The annotations supply only a title (取消队列里的一条) with no readOnly/destructive hints, so the description carries the full behavioral burden. It says nothing about whether cancellation is reversible, what happens to an item already being processed by queue_run, what the failure mode is for an unknown or already-published id, or what the response contains.

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?

One short sentence with the action front-loaded and zero filler. It is appropriately terse for a single-parameter tool, though the terseness edges toward under-specification rather than genuine structural clarity.

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, no-output-schema tool the description covers the core identity, but it omits behavioral facts an agent needs before invoking a cancellation: irreversibility, effect on in-flight queue items, and error behavior. Adequate as a minimum, not sufficient for a mutation tool with no meaningful annotations.

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% for the single required parameter (id: 队列条目 id), so the schema already explains it. The description's 按 id adds only the minimal framing that the id selects the entry to cancel, which is 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 names a specific verb (取消/cancel) and a specific resource (一条待发布内容, a pending-publish queue item), plus the keying parameter (id). This distinguishes it from sibling queue tools such as douyin_queue_list and douyin_queue_run, 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 qualifier 待发布 (pending publish) implies the operation only applies to items not yet published, which is a mild usage constraint. However there is no explicit when-to-use/when-not guidance, no mention of alternatives (e.g. queue_list to find an id), and no note on prerequisites such as login.

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