douyin_queue_list

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

The only annotation is a title, so the description carries the full burden. It reveals that the tool returns both queue content and status values, but says nothing about ordering, result size, pagination, or that it is a non-mutating read – all things an agent needs before calling a queue-inspection tool on a possibly long queue.

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 compact sentence with the resource and statuses front-loaded, followed by the use case. No filler; only mild critique is the parenthetical status list that duplicates and contradicts the schema enum.

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 single optional enum parameter with no output schema and near-empty annotations, the description covers the core ('what is listed') and the rationale, which is close to sufficient. It falls short on the status-value discrepancy and on any notion of ordering or result volume.

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 coverage is 100%, so the baseline would be 3, but the description actively introduces confusion: it lists 'running' as a status while the filter enum only accepts all/pending/done/failed, and it never mentions the 'all' default that the schema defines. The added meaning is partly incorrect rather than additive.

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 (列出队列里所有内容与状态) and enumerates the status values it reports, which distinguishes it from the queue mutators (douyin_queue_add, douyin_queue_cancel, douyin_queue_run) in the sibling list. Slightly weakened by the status set not matching the schema enum, but the intent is unmistakable.

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?

'看今天该发什么' hints at the intended use case (checking what's ready to publish today), which implies usage. However, it names no explicit alternatives or exclusions – it does not say to use douyin_queue_run to execute items or douyin_queue_cancel to remove them, leaving the agent to infer the boundary.

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