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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful non-annotation context: the tool returns original outcomes rather than current product state, requires products:read, and supports correction only for failed items with a new idempotency key. It does not describe the response shape, but the behavioral warnings are substantive.

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 compact sentences, front-loaded with the purpose and followed by workflow constraints. It is dense but efficient, with no filler, though the phrasing is slightly jargon-heavy.

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 read tool with annotations and no output schema, the description covers the workflow well but leaves the parameter meaning and return structure underspecified. An agent can infer the general use case, but must rely on the schema alone for the import_id format and expected result shape.

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 never mentions the sole parameter, import_id, or what value to supply. The schema pattern provides format hints, but the description does not compensate for the missing parameter semantics as required when coverage is low.

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 uses a specific verb ("Read") and resource ("original saved/rejected outcomes of one catalogue batch"), and adds the required scope ("products:read"). It distinguishes the operation from current-product reads and from resubmission, though "catalogue batch" is slightly less direct than naming the import record 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?

It gives clear operational guidance: read current products before resolving version conflicts, correct only failed items with a new idempotency key, and never resubmit successful items or overwrite newer edits. It does not explicitly name sibling alternatives such as the import mutation tool, but the when/when-not conditions are clear.

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