create_product

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

With no annotations provided, the description carries the full burden. It adds valuable behavioral context: products are priced in USDT and auto-converted at checkout, and digitalContent triggers automatic delivery. However, it does not disclose side effects, requirements (e.g., conditional fields), or return behavior, leaving 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?

The description is two sentences, front-loads the primary purpose, and contains no fluff. It is concise and every sentence adds useful information about what the tool does.

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 gives a solid overview but does not cover important nuances like content types (GENERAL vs SKILL) or conditional requirements. With 10 params and nested objects, more guidance would be helpful, but the schema covers parameter details, and no output schema means return values are not explained.

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 baseline is 3. The description mentions digitalContent for automatic delivery, but the schema already states 'Digital delivery content — auto-delivered after payment'. It adds no new parameter meaning beyond what the schema 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 action ('Add a digital product') and the resource ('to your store'). It distinguishes create_product from siblings like update_product and delete_product by specifying 'Add'. It also clarifies the product type as digital.

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 provides clear context: use this to add a digital product to a store. It mentions pricing and delivery behavior, giving a sense of when this tool is appropriate. However, it does not explicitly exclude alternatives or mention when to use update_product, so it misses the 'when-not' element.

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