importCatalog

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

Annotations are absent, so the description carries the full behavioral burden. It only states the import action and sources, without disclosing whether existing catalog data is replaced, whether authentication is required, or what side effects occur on the store.

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 opening clause is concise and front-loaded. However, 'high-converting 3D commerce store' is promotional rather than operational, and the second sentence is vague about the actual usage boundary, so not every phrase earns its place.

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?

With five parameters, no annotations, and no output schema, the description should tie source-specific parameters together and indicate expected outcomes. It does neither, leaving an agent unsure about prerequisites, success conditions, or side effects.

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 coverage is 100%, so the baseline of 3 applies. The description restates the source enum but does not explain conditional dependencies such as Shopify requiring shopifyStore and shopifyAccessToken, or CSV requiring csvData.

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?

States a clear verb and resource: 'Import product catalog' from Shopify, CSV, or manual input. This distinguishes it from siblings like createStore and publishStore, but the clause 'create or improve an e-commerce store' broadens the scope and could cause mis-selection.

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?

Provides an explicit trigger ('Use this when...') but it is overbroad and does not mention alternatives or exclusions. It doesn't clarify that store creation likely belongs to createStore or publishing to publishStore, leaving selection partly to inference.

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