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

With no annotations provided, the description carries the full burden — and it does thoroughly. It reveals immediate buyer visibility, the approval lock via expected_updated_at, refusal on stale products, per-call approval requirement, single-send-on-approve behavior, and no standing grant. All are critical behavioral traits beyond the name.

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 well-structured and front-loaded with the primary meaningo, but it repeats the approval concept several times across the header, 'Approval-tier, lock-checked,' and the outbound-tier notice. Still organized, every sentence earns inclusion given the high-risk operation.

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?

A high-complexity edit tool with no annotations and no output schema receives enough practical detail for an agent to decide and invoke it. It covers when to use, what it does, the locking/approval workflow, and the refusal condition. Missing return format is a minor gap.

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 has 50% coverage (, for name, product_id, companyId, expected_updated_at), and the description compensates by naming which fields are editable (title, description, tags, effectively mapping to title, description_html, tags). It also adds real-world meaning to expected_updated_at as an approval-lock semantic, though the schema already says 'read when the edit was reviewed.'

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 starts with a specific verb and resource: 'Edit a LIVE Shopify product's title, description, or tags.' This clearly differentiates it from draft-editing tools like update_shopify_ product"_draft by emphasizing 'LIVE' and the immediate buyer-visible effect.

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 explicitly states when to use: 'Use when the operator approves a change to live catalog.' It does not explicitly name alternatives or state when-not scenarios, but the live-vs-draft contrast is strongly implied by the word 'LIVE' and sibling tool existence.

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