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

Beyond annotations (destructiveHint=true, readOnlyHint=false), the description adds crucial behavior: changes take effect immediately, expected_updated_at acts as an optimistic lock refusing stale edits, and every call requires a manager's approval with per-send human rail. This goes well beyond 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 description is multi-part but each section adds necessary value: purpose, routing, and approval mechanics. It is slightly verbose but not wasteful, and the most important info (live edit, lock) is front-loaded.

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 mutation with no output schema and moderate parameter coverage, the description covers purpose, when-to-use, approval flow, and concurrency safety. Minor gaps remain (e.g., whether tags are replaced or appended, or what a successful response looks like), but agents have enough to invoke correctly.

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?

With 50% schema description coverage, the description compensates by clarifying that title, description, and tags are the editable fields. It also explains expected_updated_at's lock semantics ('refuses if the product changed since the edit was reviewed'), which is significant added meaning beyond the schema's bare ISO note.

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 ('Edit a LIVE Shopify product's title, description, or tags') and clearly distinguishes from siblings by emphasizing LIVE, immediate buyer-visible changes and approval-tier locking. This differentiates it well from draft-editing and publishing siblings.

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 'Use when the operator approves a change to live catalog' and provides routing cues ('Shopify: edit a LIVE product — approval-tier, lock-checked'). It does not name alternative draft/publish tools, but the 'LIVE' qualifier and approval context make the use case clear.

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