doubao_image_pro_result

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

With no annotations, the description carries the full burden. It correctly indicates the tool is a query (read operation) but does not disclose what happens for invalid task_id, pending results, or error states. The behavioral context is minimal.

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?

Two sentences, front-loaded with purpose, zero waste. Every word earns its place.

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 a single parameter and an output schema (per context), the description adequately covers purpose and usage condition. It lacks details on expected polling behavior (e.g., should it be called repeatedly?) but is otherwise complete for a simple query tool.

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% and the description does not formally explain the 'task_id' parameter. However, the usage guideline implicitly ties it to the taskId from the generate tool. For a single-parameter tool, this indirect explanation is weak but functional.

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 uses a specific verb (查询/query) and resource (任务结果/task result) with the model identifier Seedream 5.0 Pro. It clearly distinguishes itself from sibling tools like doubao_image_lite_result and doubao_video_result by targeting a specific model.

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 the condition for use: '仅在 doubao_image_pro_generate 超时返回 taskId 后使用' (only after the generate tool times out and returns a taskId). This gives clear context on when to use this tool versus the generate tool, though it does not cover polling behavior or alternative failure handling.

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