cancel_dataset

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

With no annotations provided, the description carries the full burden of disclosure. It mentions purge/cancel intent, but does not explain whether purge is irreversible, what permissions are required, what happens to an in-progress build, or other side effects. The generic 'Success or error message' return line adds little behavioral detail.

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 compact, front-loaded with the primary purpose, and organized into Parameters, Returns, and Example sections. There is no filler or redundant expansion beyond a helpful example.

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 one-parameter tool with an output schema, the core invocation is covered. However, because there are no annotations and the operation includes a destructive 'purge', the missing side-effect and cancellation-semantics context leaves a clear gap.

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%, but the description compensates by defining dataset_id with its type, required status, meaning, and a concrete example. This adds meaningful context beyond the raw schema.

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 first line states a specific resource and actions: 'Cancel a dataset build or purge a completed dataset.' It clearly identifies the target as a dataset, though it does not explicitly contrast with sibling tools like cancel_gravity_task, so it stops short of a 5.

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?

Usage context is implied by the resource: use this when a dataset build needs cancellation or a completed dataset needs purging. However, there is no explicit when/when-not guidance or mention of alternatives such as build_dataset, get_dataset_status, or cancel_gravity_task.

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