wafle_csv_import

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

Annotations already state idempotentHint=false and destructiveHint=false. The description adds valuable context: the tool is long-running, emits progress notifications with rows processed/total, and returns a summary with imported/updated/errors/duration. This goes beyond the annotations without contradicting them.

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 two short sentences plus a compact return summary list. It is front-loaded with the core action and avoids redundant or vague 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?

For a long-running tool with no output schema, the description covers the execution model, progress events, and return value. It does not explain the mapping parameter, but the schema does. The description is sufficiently complete for an agent to understand what to expect and how the tool behaves.

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 high (75%), with descriptions for slug, csv_url, and mapping. Timeout_seconds lacks a description but has default/min/max. The tool description does not add further semantics beyond what the schema already provides.

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 the tool imports a CSV product feed into a store with catalog_mode=csv. This specific verb+resource combination distinguishes it from siblings like wafle_products_sync_trigger and wafle_products_create_manual.

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 provides clear context by specifying the target store mode (catalog_mode=csv) and the long-running nature, implying when it applies. However, it does not explicitly mention alternative tools or situations where it should not be used.

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