reading_import_cancel

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

The description explicitly states the destructive nature of the tool ('delete its temporary upload file'), which compensates for the lack of annotations like destructiveHint. However, it does not mention reversibility or side effects on other imports.

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?

A single sentence that conveys the complete action without redundancy. Every word is necessary and contributes to understanding.

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?

The description covers the primary purpose and outcome, but given the absence of an output schema and the simplicity of the tool, it would benefit from mentioning return values or error states for completeness.

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 single required parameter uploadId has no description in the schema (0% coverage), and the description does not elaborate on what uploadId represents or its format, leaving the agent to infer context.

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 clearly states the action: cancel a chunked import and delete its temporary upload file. It uses specific verbs and resource terms, distinguishing it from other import-related siblings like reading_import_begin, reading_import_finish, etc.

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 implies when to use (when aborting an import), but does not provide explicit guidance on when not to use or alternative tools, such as reading_import_finish to complete the import instead.

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