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

Beyond the destructive/readOnly annotations, it discloses refusal behavior for live products, approval-tier behavior, and specific agent guidance about not re-asking after the approval card is shown. These are meaningful behavioral details not captured in the structured annotations.

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 first sentence is front-loaded and does the core work; the sensitive-tier block adds valuable approval guidance. A deduction is warranted because the 'Routing:' line largely repeats the first paragraph's content.

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 5-parameter mutation tool with full schema coverage, the description covers purpose, scope restriction, and approval workflow well. It does not describe the return payload, but there is no output schema and the success outcome is reasonably implicit.

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 the schema already documents price format, companyId, and gids. The description adds no new parameter semantics beyond restating that compare_at_price is optional, which the schema also conveys.

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 opens with a specific verb and resource: 'Set a variant's price ... on a DRAFT Shopify product.' It also differentiates from live repricing by stating it refuses live/ACTIVE products and that changing buyer-facing prices requires the approval-gated live tool.

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?

It explicitly says when to use the tool: 'Use when a person or agent is pricing unpublished catalog.' It also gives a when-not by explaining it refuses live products, and it points live repricing to the approval-gated live tool as the alternative.

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