tiendanube_create_product

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

With no annotations provided, the description must convey behavioral traits. It mentions supported features (multi-language, variants, etc.) but lacks details on side effects, idempotency, response format, or permissions. It does not contradict any annotations since none exist.

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 exceptionally concise with two sentences. The first sentence states the action and minimum requirements, and the second lists capabilities. No unnecessary words.

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 complexity (26 parameters, no output schema, many siblings), the description is incomplete. It does not mention the response (likely the created product), synchronous vs asynchronous behavior, error handling, or how this relates to variant and image creation tools.

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 schema already documents each parameter's meaning. The description adds minimal extra context by grouping capabilities and restating required fields. It does not significantly enhance understanding 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 clearly states it creates a product and mentions minimum requirements. However, it does not explicitly distinguish from sibling tools like tiendanube_create_product_variant, which could cause confusion when the agent needs to create a variant instead.

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 description implies usage by specifying required fields (name and price) but provides no guidance on when to use this tool versus alternatives (e.g., create_product_variant for variations), nor does it mention prerequisites like category existence.

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