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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the state precondition that cancellation is only valid pre-dispatch, and that dispatched/uncertain imports require reconciliation instead. It omits what happens to already-cancelled or in-flight uploads and any permission requirements.

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 tight sentences, front-loaded with the action and its precondition, with no filler. The second sentence partially restates the first's constraint, which is the only small redundancy.

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 destructive, idempotent mutation with no output schema, the precondition and the reconcile-versus-cancel fork are covered, but the description never tells the agent which tool to use for the dispatched case, nor does it say what a successful cancel returns or what happens to the underlying source data. Adequate but with clear routing and outcome gaps.

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 67% (projectId and idempotencyKey are documented, importId is not), and the description adds no parameter meaning at all. With one required identifier undocumented in both the schema and the description, and no clarification of where an importId comes from (e.g. source_imports), the description fails to compensate for the gap.

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?

Names a specific verb and resource (cancel a source upload) and states the guarding condition, which distinguishes it from the sibling reconcile_source_import that handles the dispatched case. It stops short of naming that sibling, so differentiation is implicit rather than explicit.

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 description gives a clear when-to-use rule ('only if it has not been dispatched to the backend') and a when-not rule ('an uncertain or dispatched import must be reconciled and cannot be released by cancellation'). It does not name the alternative tool (reconcile_source_import) the agent should route to in that case.

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