delete_animation_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 fails it. It does not say whether deletion is permanent or reversible, whether the task's artifacts (meshes, outputs) are also destroyed, what happens if the task is still running, or what permissions/ownership are required.

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 description is a single clean sentence with zero padding and the verb front-loaded, so it is concise. However, this is brevity by omission rather than efficiency — there is no content to be well-structured.

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 mutation tool with no annotations, no output schema, and 0% parameter coverage, the definition is far too thin. An agent cannot determine reversibility, side effects on related resources, or return behavior before committing to an irreversible call.

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% — task_id is an undocumented string — and the description adds no meaning about its format, source (from create/list calls), or behavior on an unknown/unowned ID. The single parameter is guessable but entirely unelaborated.

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 sentence 'Delete an animation task' is a near-verbatim restatement of the tool name delete_animation_task, adding no scope or differentiation. It does identify the verb and resource, but a reader learns nothing they couldn't infer from the name alone, and nothing distinguishes it from the ~10 sibling delete_* tools.

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 delete versus retrieve/list/stream an animation task, no preconditions (must the task be completed or cancelled first?), and no statement of consequences. The agent must infer everything from the tool name.

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