update_product

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

Description discloses partial update behavior ('Only provided fields are changed') and replacement behavior for prices ('Providing prices replaces all existing prices'), supplementing annotations (readOnlyHint=false, destructiveHint=false) without contradiction.

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. Front-loaded with verb and resource. Highly concise and structured.

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?

Covers the key behavioral aspects (partial update, price replacement). Could mention that other fields are optional or that the response format varies, but not necessary given 100% schema coverage and no output schema. Minor gap.

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?

Adds significant meaning beyond the schema: clarifies that it's a partial update and that prices array replaces all existing prices. Schema coverage is 100%, but these behavioral nuances are not captured in the schema alone.

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?

Description clearly states the action 'Update an existing Billy product' and specifies key behaviors like partial update and price replacement. Distinct from sibling tools like create_product and other update tools.

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?

Implied use for modifying an existing product, but no explicit mention of when not to use or alternatives like create_product for new products. Could be improved but still clear.

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