delete_retexture_task

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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing beyond the verb. It does not state whether deletion is permanent, whether in-progress tasks can be deleted, whether output files are purged, or what happens if the task_id is unknown — all critical for a destructive tool.

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?

The single sentence is front-loaded and waste-free, but at four words it is undersized for a destructive operation rather than genuinely efficient. Nothing is buried, yet nothing useful is added either.

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?

With no annotations, no output schema, and an undocumented parameter, the description is the only source of behavioral information for a destructive tool and provides none of it. An agent cannot tell whether the call is recoverable or what it returns.

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 the single required parameter task_id is documented neither in the schema nor in the description. The description does not say where to obtain the id (e.g., from create_retexture_task or list_retexture_tasks) or what format it takes.

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 ('Delete') and resource ('retexture task'), which cleanly separates it from the retrieve_/list_/create_/stream_ retexture siblings in the tool list. It stops short of saying what exactly is removed (task record only vs. generated assets), but the operation itself is unambiguous.

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 call this rather than letting a task expire, no prerequisites, and no stated alternatives. The only implied usage is 'you have a task_id and want it gone', which the agent must infer.

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