stream_multi_image_to_3d_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 discloses nothing: not whether the call blocks, how the stream terminates, what happens on task failure, or what the timeout parameter governs. It restates the name and stops.

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, front-loaded and free of padding. It is under-specified rather than verbose, so the brevity earns little credit.

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?

A streaming tool with no output schema, no annotations, and no parameter documentation needs the description to explain the stream's shape, termination, and error behavior. None of that is present, so an agent cannot call this reliably.

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% and both parameters (task_id, timeout) are undocumented in the schema. The description adds no meaning to either — not even the timeout unit or whether it caps stream duration.

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 verb ("Stream updates") and a resource ("multi-image-to-3d task"), and the word "stream" does distinguish it from the sibling retrieve_multi_image_to_3d_task. However, it never explains what a "stream" is here (SSE, incremental polling, long-lived connection), leaving the core action vague.

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?

No guidance on when to stream versus calling retrieve_multi_image_to_3d_task, no preconditions, and no mention of what the caller should do with the updates. The sibling set makes an alternative obvious, yet the description never references it.

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