cancel_integration_setup

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

With no annotations, the description carries the behavioral burden, and 'changing nothing' is a meaningful non-mutation guarantee. This addresses the main behavioral risk for an agent considering whether the call has side effects.

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 eight words, front-loads the action, and tucks the key safety guarantee into an appositive. There is no filler.

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 two-parameter cancellation tool with an output schema, the description conveys the intent and safety profile in one sentence. It doesn't detail how driver_id selects the setup, but the schema and sibling structure make that inferable.

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 the description does not explain driver_id or host. The property names are somewhat self-explanatory, but the description adds no parameter-level meaning to compensate for the missing schema descriptions.

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 names a clear action ('Abandon') and a specific resource ('in-progress setup flow'), and adds the clarifying guarantee 'changing nothing'. This distinguishes it from sibling setup actions like answer_integration_setup and confirm_integration_setup.

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?

It states the clear context for use: an in-progress setup flow. It doesn't explicitly name alternatives or exclusions, but the domain of 'setup flow' makes the selection obvious among siblings.

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