set_product_prices

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

With no annotations, the description carries the full burden and does disclose a real prerequisite: apply requires the 'master safe-write gate'. But it leaves the safety mechanics opaque — the dryRun default, idempotency key, previewToken, and the expected*hash guards are all unaddressed.

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 tight sentences, front-loaded with the preview/apply distinction and followed by the gating condition. Both sentences earn their place; the terseness is only a problem because content is missing, not because of padding.

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 nested price rows, idempotency, concurrency hashes, and no annotations or output schema, the description is far too thin to guide a correct invocation.

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 0% across 11 parameters, so the description must compensate and largely fails to. 'Preview or apply' loosely maps to dryRun/mode, but productId, prices, removeProductPriceIds, idempotencyKey and the various hash/timestamp guards are never explained.

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+resource combination ('Preview or safely apply product price rows') and distinguishes the read sibling get_product_prices from the write path. It's clear, though it never names the sibling it is contrasting against.

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?

'Preview or safely apply' implies the two operating modes, and 'Apply requires the master safe-write gate' gives a precondition for the write path. However, it doesn't say when to choose preview versus apply, or point to get_product_prices/list_pricing_schemes for discovery.

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