doubao_video_result

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

With no annotations, the description must disclose behavioral traits. It only states the purpose and usage condition but does not mention whether the operation is read-only, how it handles in-progress or failed tasks, polling behavior, rate limits, or authentication requirements. The timeout condition is hinted but not elaborated.

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?

The description is two sentences with no wasted words. It front-loads the tool's purpose and then provides the usage condition. Every sentence earns its place, making it highly efficient.

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?

Given the tool has an output schema, return values are covered. The description provides the essential context (when to use and what it does) but lacks details on error handling, polling, or what happens if the task isn't ready. It is minimally viable but not thorough.

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 0%, so the description must compensate. It does not describe the 'task_id' parameter beyond its existence, leaving the agent without format details, how to obtain it, or what values are valid. The reference to 'returns taskId' is context but does not define the parameter's semantics.

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 clearly states the tool queries the result of a Doubao video generation task. It specifies the resource ('video generation task result') and the verb ('query'), distinguishing it from siblings like gpt_image_result or doubao_video_generate. The mention of the timeout condition adds further clarity.

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 description explicitly states when to use: '仅在 doubao_video_generate 超时返回 taskId 后使用' (only use after doubao_video_generate times out and returns a taskId). This provides concrete guidance and implies that the tool should not be used in other scenarios, effectively differentiating it from similar result-query tools.

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