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

Annotations already declare destructiveHint/idempotentHint/openWorldHint, so the safety profile is covered; the description still adds real substance by revealing partial-update semantics ('only the fields you pass are sent') and the Shoprocket-specific requirement that name must be resent on every update or the current value is lost. It also discloses the concrete endpoint, though it says nothing about the response or error behavior.

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?

Three short sentences, zero waste, with the write classification and field scope front-loaded before the operational gotcha. Every sentence carries information an agent would otherwise have to infer.

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 a twelve-parameter mutation with no output schema, the description covers the critical failure mode (dropping name) and the partial-update contract, which is enough for a correct call. It stops short of describing the response shape or failure handling, which is the only remaining gap given the rich schema and annotations.

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 all twelve parameters including the name requirement and cents-based price are already documented in the schema. The description echoes the name-required gotcha but adds no formatting, unit, or interaction detail beyond the structured fields, so the baseline 3 applies.

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 plus resource and enumerates the changeable fields (price, stock quantity, description, status), which separates it cleanly from create_product, get_product, and the update_* siblings on other resources. The 'WRITE:' prefix makes the operation class unmistakable at a glance.

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?

Usage is implied — you use it to change an existing product — and there is useful operational guidance (pass the current name, only passed fields are sent), but no explicit when-not-to-use or named alternative such as 'use shoprocket_create_product to create' or 'use shoprocket_get_product to read first'.

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