stream_image_to_3d_task

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

With no annotations, the description carries the full behavioral burden. 'Stream updates' hints at an incremental/streaming response, but nothing is said about whether the call blocks until task completion, how updates are delivered or terminated, what happens on error, or how the timeout parameter behaves.

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?

It is a single front-loaded sentence with no waste, but that brevity comes at the cost of missing semantics rather than from trimming redundancy. Efficiently worded yet under-specified.

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 annotations, no output schema, and 0% parameter coverage needs the description to explain the update stream and the timeout, and it does neither. An agent cannot predict the response shape or termination behavior from this definition.

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 both parameters (task_id, timeout) are undocumented anywhere. The description says nothing about which task identifier is expected or what the timeout controls, leaving one parameter entirely opaque.

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 states a specific verb ('Stream updates') and resource ('image-to-3d task'), which cleanly separates it from create/retrieve/list siblings in the image-to-3d family. It does not explicitly contrast itself with retrieve_image_to_3d_task, so the agent must infer the difference between streaming and one-shot retrieval.

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 statement of when to use this versus retrieve_image_to_3d_task or list_image_to_3d_tasks, no prerequisites, and no indication of when streaming is preferred. The only guidance is the implied 'stream' semantics of the name.

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