justhandled_shopify_product_csv_preflight

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

With no annotations, the description carries the full burden. It discloses a significant behavioral trait (costs $0.05 USDC on Base mainnet) and the nature of the check, but does not state whether the operation is read-only, what the return format looks like, or any potential side effects beyond the cost.

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, well-structured sentence that leads with the action and key checks, then adds the cost detail. Every word adds value, with no redundancy or filler.

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?

Given the tool's moderate complexity (4 parameters, no output schema), the description covers the core checks and cost but omits critical context: what the tool returns, how to interpret results, and the role of parameters like mode and existing_handles. It is enough for basic understanding but not fully sufficient for safe and correct usage.

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 must compensate. It provides no direct explanation of the four parameters, their formats, or when they are required. The mention of 'overwrite hazards' vaguely relates to parameters like mode and existing_handles, but not explicitly, leaving the agent to infer semantics from the schema alone.

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 clearly states a specific action ('Check') and a specific resource ('normalized Shopify product rows'), and lists four distinct check categories (missing identity fields, duplicate SKUs, unsafe image URLs, overwrite hazards). This clearly distinguishes it from sibling preflight tools targeting other domains.

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 usage context is implied by the tool name and description—use it to preflight Shopify product CSV data before import—but there is no explicit 'when to use' or mention of alternatives. No exclusions or comparisons to sibling tools are provided.

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