Update Product

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

Annotations are present and include idempotentHint=true and destructiveHint=false, which provide safety profile. The description adds the key behavioral detail that only provided fields are changed (partial update). No contradictions. Could be improved by noting error behavior if product ID not found.

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, front-loaded sentence communicates the core purpose and key behavioral constraint ('Only provided fields') with no wasted words.

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?

Without an output schema, the description should indicate what the tool returns (e.g., updated product object). It also lacks error handling guidance. These gaps reduce completeness for an update operation with 10 parameters.

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 all parameters described. The description adds no extra meaning beyond the schema, which is acceptable given the schema is self-sufficient. 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?

Tool name and description clearly identify the action (update) and resource (product) and differentiate from siblings like create, delete, get, and list by specifying 'Update an existing 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 states 'Only provided fields are changed', indicating a partial update pattern. While it doesn't explicitly contrast with sibling tools, the verb 'update' and context of existing product imply when to use. A brief mention of when to use create vs update would improve clarity.

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