update_inventory_product_photo

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

Annotations already indicate non-readonly, non-destructive, idempotent. Description adds the constraint photoId must belong to resolved product but doesn't elaborate on side effects of updating fields (e.g., clearing description via null). Acceptable but unremarkable.

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 efficient sentences. First sentence states action and affected fields; second adds essential constraint. No fluff or redundancy.

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?

Description covers core purpose and constraint. For a simple update tool with well-documented params and output schema, it's sufficient. Could mention how product resolution works but schema covers that.

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 100%, so baseline is 3. The description doesn't add meaning beyond what's in param descriptions (e.g., photoId requirement repeated). No additional semantic value.

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?

Clearly states it updates description and/or pinned state for a photo attached to an inventory product. Distinguishes from sibling tools like add_inventory_product_photo and delete_inventory_product_photo by focusing on update and specific fields.

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?

Provides constraint that photoId must belong to resolved product but lacks explicit guidance on when to use this tool versus alternatives like add/delete/other update tools. No 'when-not' or alternative names mentioned.

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