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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add context — and it does: partial data is retained ('what it already brought across stays'), the caller must be the workspace owner, and a human confirmation step is involved. It does not say what happens when the id is not cancellable, but the core destruction and authorization semantics are 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?

Three short sentences, front-loaded with the action and its state constraint, then consequences, then permissions. Nothing redundant or padded.

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 destructive mutation with no output schema, the description covers state precondition, data retention, authorization, and confirmation — the essentials. The only meaningful gap is the identity/format of the 'id' argument.

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 description must explain the single 'id' parameter, but it never states that the id identifies the provider import or where to obtain it. An agent can infer the target from context but is not told the expected identifier form.

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?

States a specific verb ('Stop') plus the exact resource ('an import from another email provider') and narrows scope to imports 'still waiting or running'. It implicitly separates itself from the generic cancelImport by specifying the provider-import case, though it never names that sibling explicitly.

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?

Gives a clear applicability condition ('still waiting or running'), which implies finished or failed imports are out of scope, and adds the owner-only and confirmation preconditions. It stops short of naming an alternative tool for the cases it excludes.

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