Add Product

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the mutation ('Create') but does not disclose side effects such as duplicate SKU handling, idempotency, permission requirements, or whether existing data is affected. The agent knows it is a write operation but nothing about its behavioral edge cases.

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 a single sentence that front-loads the action and efficiently lists all fields in a compact order. No redundant words, no filler. Every part contributes to conveying the core operation.

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 5-parameter create tool with no annotations and no sibling differentiation, the description is minimally viable but incomplete. It correctly identifies the operation and fields, and an output schema exists to document return values. However, it lacks critical operational context such as duplicate handling, required permissions, or when to prefer the sibling add_product_smart.

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 0%, so the description must compensate. It lists all five parameters and marks description as optional, which clarifies the confusing optionality expressed in the schema's convoluted anyOf. However, it adds no deeper semantic meaning beyond the parameter names, and the schema already defines types and constraints.

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 a specific verb ('Create') and resource ('a new product'), and enumerates the key fields (sku, name, optional description, price, quantity). It is unambiguous about the operation, but it does not differentiate from the sibling tool add_product_smart, both of which appear to create products.

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 no guidance on when to use this tool versus add_product_smart or how it differs from get_product_by_id or delete_product. There is no mention of conditions, alternatives, or exclusions, leaving the agent to infer usage from the tool name alone.

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