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

The description adds substantial behavioral context beyond the annotations: it discloses the ACTIVE→DRAFT state change, buyer-visible impact, approval requirement, lock-checking with expected_updated_at, and the 'exactly once on approve' send behavior. This goes well beyond the destructiveHint and readOnlyHint annotations, explaining what actually happens and what operational guardrails apply.

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 core action is front-loaded and clear, but the description repeats itself across the main paragraph, the routing line, and the outbound-tier block: 'take a live product DOWN', 'approval-tier', and 'lock-checked' all appear more than once. The outbound-tier block is operationally valuable but verbose, and some sentences could be merged without losing meaning.

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 destructive, approval-tier mutation with three fully documented parameters and no output schema, the description provides enough context to call the tool correctly: what it does, when to use it, what guardrails apply, and what the approval flow looks like. It does not describe success/failure responses, but that is a minor gap given the operational guidance already present.

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 coverage is 100%, so the schema already documents all three parameters. The description adds extra meaning by explaining that expected_updated_at is used for lock-checking and was 'read when the takedown was reviewed', which clarifies why the parameter exists and how it prevents race conditions. This goes beyond the schema's basic 'The product's updatedAt' description.

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 states a specific verb and resource: 'Take a LIVE Shopify product off the storefront' and explicitly names the status transition 'ACTIVE → DRAFT'. It distinguishes itself from siblings like publish_shopify_product by framing the action as 'take a live product DOWN' and specifying the operator decision context.

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 description gives an explicit when-to-use condition: 'Use when the operator decides a live product comes down.' It also explains the approval-tier and lock-checked nature, which signals when this tool is appropriate. It does not explicitly name alternatives or state when not to use it, but the routing line makes the direction clear.

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