stream_image_to_image_task

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

No annotations are provided, so the description carries the full behavioral burden and it says almost nothing: it does not describe the streaming mechanism, whether the stream terminates when the task completes, what happens on timeout, or whether the call is blocking or long-lived. "Stream" implies incremental delivery but nothing about error behavior or termination is disclosed.

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?

A single front-loaded sentence with no filler, which is structurally clean. But for a streaming tool with a timeout parameter, one sentence is undersized rather than concise — the terseness costs the agent information rather than saving it.

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 no annotations, no output schema, and 0% parameter coverage, the description needed to explain streaming semantics, termination, and timeout behavior. It supplies none of these, so an agent cannot call it correctly without guessing.

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 0%, so the description must compensate, and it does not. task_id is self-explanatory, but timeout — its unit, default, and whether it bounds the whole stream or just the initial connection — is completely undocumented.

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 ("Stream updates for an image-to-image task"), so an agent knows it is the streaming counterpart for image-to-image tasks. However, it does not distinguish itself from the closely related siblings retrieve_image_to_image_task and list_image_to_image_tasks, leaving the stream-vs-retrieve-vs-list choice to be inferred from the name alone.

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?

There is no guidance on when to use streaming versus retrieve_image_to_image_task, nor whether the task must be created first or already be running. The agent must infer the workflow entirely from the sibling names.

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