delete_remesh_task

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

With no annotations, the description carries the full burden for a destructive operation, yet it says nothing about permanence, whether deletion is reversible, what happens to an in-progress task, or what error is returned for an invalid task_id. 'Delete' does signal mutation, so it is not misleading — just severely under-disclosed.

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?

One short, front-loaded sentence with zero filler. It is efficiently worded; the problem is omission, not verbosity.

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?

A destructive, single-parameter tool with no annotations and no output schema needs the description to cover irreversibility, error conditions, and id provenance. None of that is present, so an agent cannot call it confidently in edge cases.

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%, so the single task_id parameter is undocumented in structured data. The description adds no format, source (where to obtain the id), or validity constraints, leaving the agent to guess whether this is the id from create_remesh_task or a different handle.

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 states a specific verb and resource (delete a remesh task), which separates it cleanly from retrieve_remesh_task, list_remesh_tasks, and create_remesh_task in the sibling set. It stops short of explicitly naming those siblings as the alternatives, so it is clear but not maximally differentiated.

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 versus siblings, no prerequisites (does the task need to be finished or stopped first?), and no mention of what happens to a running task. The usage context is only inferable from the name.

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