delete_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 discloses nothing: not that the operation is destructive and irreversible, what happens to an in-progress generation, whether the task data is recoverable, or what an error/response looks like. Only the word 'Delete' implies mutation, and that comes from the name.

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 sentence with zero padding, but its brevity reflects under-specification rather than efficiency — it is front-loaded with nothing but a restated name.

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 destructive single-parameter tool with no annotations, no output schema, and zero schema description coverage, the description leaves an agent without the information needed to call it safely or correctly; it should at minimum state irreversibility and where task_id comes from.

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 the single required parameter, task_id. The description says nothing about its format, where to obtain it (presumably from create_/list_image_to_3d_tasks), or whether unknown IDs error out, so it fails to compensate for the undocumented schema.

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 names a specific verb and resource ('Delete an image-to-3d task'), which lets an agent separate it from delete_remesh_task or delete_rigging_task by resource type. However, it is essentially the tool name with spaces added — no scope, no effect, no distinguishing detail beyond what the name already conveys.

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, list_image_to_3d_tasks, or when deletion is appropriate. No prerequisites (e.g., task must be complete or can be in-flight) and no mention that deletion is irreversible.

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