Update product price

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

With no annotations, the description carries the full burden of transparency. It only states that the price is changed and mentions sale-price handling, but it does not disclose side effects, required permissions, reversibility, or impact on other product data like inventory or variant status.

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?

The description is a single, front-loaded sentence that provides the core purpose and a practical use case without any filler or redundant repetition of the tool name.

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?

The tool is a mutation with no annotations and no output schema, and the description does not cover parameter details, side effects, or any prerequisites. It provides a clear overall purpose but is insufficient for an agent to confidently invoke the tool correctly in all contexts.

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%, so the description must compensate. It does clarify the role of 'price' as the price being changed, but it does not explain 'variant_id' or 'manage_number', nor does it clarify the expected format of the price (string vs number) beyond the schema.

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?

The description clearly states the tool changes the product price and mentions the specific use case of setting/restoring sale prices. It distinguishes the tool by its focus on price, though it does not explicitly contrast with sibling tools like rms_patch_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 phrase 'used when setting/restoring sale prices' gives a clear intended context, but there is no explicit guidance on when not to use it or how it differs from sibling update tools. The usage is largely implied rather than explicitly delineated.

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