ecommerce_createPhysicalProductV1

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

Without annotations, the description carries the full burden. It reveals the product is published and single variant, but omits behavioral traits like side effects (e.g., inventory impact), authentication needs, or error conditions. Moderate transparency with notable gaps.

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?

A single, 14-word sentence that is front-loaded and contains no superfluous information. Every word earns its place, and the structure prioritizes the key action and attributes.

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?

The description lacks information about the return value (e.g., product ID), error handling, or invocation context. Given no output schema and moderate complexity, it is incomplete and leaves important gaps for an agent.

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% with clear parameter descriptions. The description adds context (published, single variant, store currency) but does not significantly enhance parameter meaning beyond the schema. Baseline score of 3 is appropriate.

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 creates a published physical product with a single variant priced in store currency. It uses a specific verb ('Create') and resource ('physical product'), distinguishing it from siblings like 'ecommerce_createDigitalProductV1'.

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 use for physical products but does not explicitly state when to avoid it or mention alternative tools. No guidance on prerequisites or exclusions is provided, making it adequate but lacking explicit when/when-not instructions.

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