reading_import_cancel

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

With no behavioral annotations other than a title, the description carries the burden of disclosing side effects. It clearly states that the operation cancels the import and deletes the temporary upload file, which is meaningful destructive context. It does not mention idempotency, irreversibility, or what happens to already-uploaded parts, but the core effects 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?

The description is a single, front-loaded sentence with no filler. It names the action and the key side effect efficiently, earning its place entirely.

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 tool, the description gives the basic purpose and a key side effect, but it omits usage timing relative to the sibling import tools and the source of the uploadId. These are meaningful gaps despite the tool's simplicity.

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 needs to compensate for the single 'uploadId' parameter, but it does not mention it at all. The parameter name is somewhat self-explanatory, but the description never says the uploadId is the import identifier or how to obtain it, leaving a 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?

The description states a specific action, 'Cancel a chunked import', and adds the concrete consequence of deleting the temporary upload file. This clearly distinguishes it from the import lifecycle siblings such as reading_import_begin, reading_import_part, and reading_import_finish.

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 no explicit guidance on when to use this tool versus alternatives, such as 'use reading_import_finish to complete successfully' or 'use this when aborting an import'. The intended usage is only implied by the verb 'cancel' and the sibling tool names.

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