stream_text_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, yet it says nothing about streaming semantics: how long the stream runs, what terminators exist, whether it blocks, or what happens on timeout/an invalid task_id. 'Stream updates' is the only behavioral signal offered.

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 short sentence with no wasted words, but the brevity reflects under-specification rather than efficiency; nothing is front-loaded beyond the bare purpose.

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 streaming tool with no annotations, no output schema, and undocumented parameters, the definition leaves critical gaps: stream lifetime, update payload shape, and timeout behavior are all unaddressed.

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% for both parameters. The description never mentions 'timeout' at all, and task_id is only obliquely implied by 'for a text-to-image task' — no format, validity, or effect is described.

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 ('Stream') and a specific resource ('text-to-image task'), which separates it from the create/retrieve/list/delete text-to-image siblings. It does not, however, explain how 'stream updates' differs from retrieve_text_to_image_task or what an 'update' consists of.

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 choose streaming over retrieve_text_to_image_task, no mention of prerequisites (e.g., a task must already exist and be in progress), and no exclusions. The agent must infer the whole usage decision from the tool name.

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