cancel_gravity_task

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the concrete effect 'stop data collection' and mentions success/error messages, but it does not cover idempotency, permissions, reversibility, whether already-completed tasks can be canceled, or what happens to data collected before cancellation.

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 and front-loaded with the core purpose. The parameter explanation, return line, and example each earn their place without redundancy or fluff.

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-required-parameter cancellation tool, the description is nearly complete: it names the effect, documents the parameter, gives an example, and mentions the return type. It lacks only a small amount of behavioral context, such as whether cancellation preserves collected data or requires special permissions, but an agent has enough to invoke it correctly.

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 input schema has 0% description coverage, but the description documents the single parameter's purpose, marks it required, and provides a concrete example value. This fully compensates for the bare schema in this simple one-parameter case.

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 ('Cancel') with a specific resource ('a running Gravity task') and adds the effect 'stop data collection.' It is clearly distinguishable from siblings like create_gravity_task and get_gravity_task_status at a glance.

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 phrase 'a running Gravity task' implies that this tool is for tasks currently in progress, but it does not explicitly say when to prefer this over cancel_dataset or when not to use it. No alternatives or exclusions are mentioned.

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