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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so "Read-only; changes nothing" mostly restates structured data. The one genuine addition is the data-format note ("Money is integer minor units (cents)"), which helps interpret inspected sample values, though it is terse.

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, purpose front-loaded, nothing bloated. Slight deduction because "Read-only; changes nothing" duplicates the annotations and doesn't earn its place against structured data that already carries the safety profile.

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?

There is no output schema, so the description field's terseness means it doesn't explain what the agent receives; the return-shape detail (columns, sample rows, mapped fields) sits in the schema description instead. Annotations cover safety, and the schema covers inputs, so the definition is workable but the description field alone leaves the output side unstated.

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 100% and each parameter (url, source, record) is well documented in the schema itself, so the baseline is 3. The description adds no parameter-level meaning beyond the schema.

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 gives a clear verb+resource ("Read a product file") and scopes it to the pre-import inspection step, which separates it from imports_create/imports_run. However, it never names the sibling it complements, so the differentiation from the other imports_* tools is left implicit.

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?

"before importing it" implies timing, but no explicit when-to-use/when-not or named alternative appears in the tool description. The clearer routing hint ("Use before imports.create") lives in the schema description rather than the description field itself.

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