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

Annotations already mark destructiveHint=trueathed, but the description adds significant unexplained behavior: the expected_updated_at concurrency lock ('refuses if the product changed since'), the per-call approval card with 'sends exactly once on approve', and 'no standing grant'. These are critical for the agent to call correctly and are not visible in 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?

Organized into three compact, purposeful sections: main action, routing summary, and approval policy. Minor redundancy between 'Publish a DRAFT Shopify product LIVE' and 'make a draft product LIVE', but nothing wasted.

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?

Covers action, trigger condition, requisite parameter semantics, concurrency lock, approval workflow, and invocation policy ('call on the first clear ask, do not re-ask'). No output schema exists, so return format is not required; the description is complete enough for 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 covers all 3 parameters with descriptions (100% coverage). The description adds real value by explaining that expected_updated_at is not just a timestamp but a lock: it must come from the reviewed read and the tool refuses if the product changed, ensuring 'what was approved is exactly what ships'.

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 ('Publish'), resource ('DRAFT Shopify product'), and result ('LIVE to buyers (status → ACTIVE)'). Clearly distinguishes from siblings like update_shopify_product_draft or unpublish_shopify_product by focusing on the draft-to-live transition.

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?

Provides an explicit trigger: 'Use when the operator green-lights a drafted product going live.' Does not name alternative tools, but the condition is unambiguous and tells the agent exactly when to invoke.

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