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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower. The description still adds real behavioral value beyond them: partial-update semantics and a data-persistence risk (edits on synced products can be overwritten). It stops short of describing failure behavior or what is returned.

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 short sentences, mutation scope front-loaded, with the sync caveat as the closing sentence. No filler, no repetition of schema metadata.

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 an 11-parameter mutation tool with no output schema and very low schema coverage, the description covers the essentials (what is editable, partial-update behavior, sync risk) but omits parameter formats and any statement of what a successful call returns or how errors surface. Adequate but with clear gaps.

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 only 18%, so the description carries extra burden. It partly compensates by naming the nine editable fields (mapping 'type' to productType), which is genuinely helpful. But it adds no format or constraint detail for price (number-or-string), tags (array, max 50), currency codes, or max lengths, so the gap is only partially closed.

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?

States a specific verb ('Changes') plus the exact resource and enumerates the mutable fields (name, description, URL, image, price, currency, tags, type, vendor). An agent can distinguish it from add_product/delete_product/get_product without opening the schema. It does not, however, explicitly contrast itself with update_product_sync_settings or hide_product, so it falls short of a 5.

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?

Gives useful conditional context ('Only the fields given are changed' and 'A synced product's edits may be overwritten by the next sync'), which is effectively a caveat about when the edit may not persist. It never names an alternative tool or an explicit precondition, so usage is implied rather than directed.

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