Delete an Actor 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 of behavioral disclosure. It usefully explains that runs and datasets produced by the task are preserved, which is an important non-obvious side effect. However, it does not mention irreversibility, required permissions, or what kind of response to expect.

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?

Two short sentences with no redundant wording. The action is front-loaded, and the second sentence earns its place by clarifying a meaningful side effect that an agent would otherwise not know.

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 low-complexity one-parameter delete tool with no output schema and no annotations, the description covers the core action and the most important behavioral consequence. It is concise and sufficient for an agent to understand what will happen, though it omits return-value and permission details.

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?

The schema declares one required string 'id' with no description, and schema description coverage is 0%, so the description must compensate. It indirectly indicates that 'id' refers to the saved task being removed, which is sufficient given the single simple parameter, but it does not explicitly document the parameter or its origin/format.

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 uses a specific verb ('Remove') and resource ('a saved task'), and immediately clarifies the scope by stating that runs and datasets are kept. This distinguishes it from sibling tools like delete-schedule or cleanup operations, making the tool's purpose immediately clear.

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?

The usage context is only implied: use this when you want to remove a saved actor task. It does not explicitly contrast with siblings such as get-actor-task or run-actor-task, nor does it state when not to use the tool.

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