retrieve_multi_image_to_3d_task

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

No annotations exist, so the description carries the full disclosure burden, and it only says it returns status and result. It does not describe possible task states, what 'result' contains, whether the call blocks, what happens for an unknown/expired task_id, or any auth/rate-limit behavior.

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 tight sentence with the resource and returned data front-loaded. Nothing is wasted, though there is also very little content.

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 simple one-parameter status getter with no output schema, the description is minimally adequate, but it omits return shape and state semantics that an agent needs to act on the result.

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?

One required parameter at 0% schema description coverage, and the description adds no meaning beyond implying task_id identifies a multi-image-to-3d task. It does not say where the id comes from (create response) or its format.

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?

Specific verb 'Retrieve' plus resource 'multi-image-to-3d task' plus scope 'status and result'. The family naming convention (create_/list_/stream_/delete_multi_image_to_3d_task) makes it distinguishable from siblings, though the description never names an alternative explicitly.

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?

Usage is implied rather than stated: an agent infers you call this after create_multi_image_to_3d_task to poll status. There is no explicit guidance on when to prefer stream_multi_image_to_3d_task over polling, nor on retry/backoff expectations.

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