update_product

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

With no annotations, the description adds the critical partial update detail but omits other important behaviors such as required permissions, side effects (e.g., webhooks), or error handling for invalid fields.

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?

Two sentences, no wasted words, directly conveys the core functionality. Front-loaded with the action and key behavior.

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 complexity of updating a product with 7 parameters and no output schema, the description adequately covers partial update but lacks mention of return value or validation outcomes. Incomplete for a mutation 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's partial update note adds marginal context beyond the schema's field descriptions, but not enough to raise the score.

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 updates an existing product and emphasizes partial update behavior, distinguishing it from related tools like create_product or delete_product.

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 explicitly mentions that only provided fields are changed, giving a clear usage pattern. However, it lacks direct comparison with alternative tools or when-not-to-use scenarios.

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