douyin_queue_add

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

No safety annotations beyond a title, so the description carries the burden. It usefully discloses the deferred-execution model (a daemon or douyin_queue_run performs the actual publish at the scheduled time), but says nothing about auth requirements, what happens if the scheduled time passes while offline, or whether queued entries can be edited/cancelled.

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?

Three short sentences, front-loaded with the action, then the execution mechanism, then the operational use case. Little waste, though the parenthetical script path is somewhat implementation-specific for an agent-facing description.

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?

Covers the core action and the post-queue execution path, which is the key unstated behavior for a scheduling tool. However, with 8 parameters and no output schema, an agent still lacks the return value (e.g. queue item id), auth prerequisites, and the relationship to the list/cancel 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 100%, so the schema already explains kind, files, cover, scheduleAt, topics and dryRun. The description only adds the video-vs-images distinction already implied by the enum, so it adds little beyond the structured fields — baseline 3.

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: '把一条准备好的内容排进定时发布队列（视频或图文）', which clearly separates it from the immediate-publish siblings douyin_publish_video / douyin_publish_images. It does not explicitly name those siblings as the immediate alternative, so it falls just short of a 5.

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?

Gives an explicit usage context ('适合“一次排一周内容”的运营节奏') and names the execution path (queue daemon or douyin_queue_run). It does not mention douyin_queue_list / douyin_queue_cancel for inspecting or removing queued items, so the guidance is clear but not exhaustive.

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