delete_rigging_task

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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not whether deletion is permanent, whether in-flight/streaming tasks can be deleted, whether associated assets are removed, or what permissions are needed. For an irreversible mutation this is a serious gap.

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 short sentence with no filler and no buried information, which is structurally fine. However, the brevity reflects under-specification rather than economy of expression, so it only earns a middling score.

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 zero annotations, no output schema, and undocumented parameters, a destructive tool needs the description to explain consequences and preconditions; none are present. An agent would be guessing about irreversibility and valid task states.

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 there is a single required parameter, task_id, whose meaning and accepted format the description does not explain. The parameter name is largely self-evident, which prevents a 1, but nothing is added.

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 restates the tool name almost verbatim: "Delete a rigging task" for delete_rigging_task. It does identify the resource (rigging task) and the action (delete), so an agent can guess intent, but it adds no scope or distinguishing information against the many 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 use this tool versus the other delete variants (delete_animation_task, delete_retexture_task, etc.) or versus leaving a task alone. No prerequisites, no state conditions, no mention of when not to use it.

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