ecommerce_createPhysicalProductV1

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

With no annotations, the description carries the full burden. It states the product will be 'published' but does not explain implications (e.g., immediate availability), prerequisites (store existence), or error cases. Ambiguity around 'single variant' leaves behavioral 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?

Extremely concise—single sentence, 14 words. Front-loaded with key action. However, could include a bit more context without sacrificing brevity (e.g., variant implications).

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?

No output schema, but description fails to mention return values or common outcomes. Missing context about store existence requirement, publish behavior, and potential errors. Incomplete for a creation tool.

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 baseline is 3. The description adds minimal value beyond schema: 'priced in store currency' aligns with the currency parameter's default behavior. No significant additional semantics for parameters.

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 distinguishes from digital product creation (e.g., ecommerce_createDigitalProductV1) but does not explicitly mention alternatives or define 'single variant'.

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?

No guidance on when to use this tool versus siblings like ecommerce_createDigitalProductV1. No prerequisites, context, or when-not-to-use information provided.

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