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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. But the description adds nothing about what destruction means here — whether mode=refresh overwrites existing drafts, how take_over and expected_revision guard concurrency, or that an idempotency_key is required for retry safety. On a destructive mutation that is a meaningful gap.

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?

It is short and front-loads the core action, so it is not bloated. But the second half is undecipherable noise that consumes a sentence without adding usable information.

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, open-world import with five required parameters, no output schema, and zero schema descriptions, the definition should explain concurrency, idempotency, and refresh semantics. Essentially none of that is present.

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% across 8 parameters, and the description supplies no parameter meaning at all. Non-obvious fields like expected_revision, take_over, mode enum values, and the shopify_connection union are left entirely unexplained.

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 first clause gives a concrete verb and resource ('Import Shopify products') plus a destination ('build drafts'), which is enough to distinguish it from catalog_list or catalog_update. However, the trailing fragment 'guides_get commerce/api import' is garbled and reads like an accidental tool-name leak rather than a clarifying statement.

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?

There is no stated condition for choosing this over catalog_list, commerce_api, shopify_query, or assets_import. The only pointer is a malformed reference to guides_get, which does not tell an agent when this tool is the right call.

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