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

With no annotations provided, the description carries the full disclosure burden and does so thoroughly: it declares the blast radius, the approval-tier requirement, the expected_updated_at concurrency lock, the theme-name typed-back confirmation, and the per-call approval card with no standing grant. An agent understands the operational consequences of invoking this tool before calling it.

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 front-loaded with the highest-value warnings and then gives operational rails. It is somewhat repetitive — 'approval-tier' appears three times across the paragraphs — so it is not perfectly tight, but every paragraph conveys critical, non-obvious operating instructions.

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 the highest-blast-radius action in the connector, the description covers purpose, precondition (theme must be unpublished), approval requirement, concurrency lock, double confirmation, and exact send behavior on approval. No output schema exists, but nothing the agent needs to call this action correctly is missing.

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%, which sets a baseline of 3, and the description adds meaningful 'why' semantics on top: expected_updated_at is explained as a lock, and confirm_theme_name as the double-confirmation mechanism. These rationales are not evident from the schema alone.

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 highly specific verb+resource — publishing an unpublished Shopify theme as the LIVE storefront — and emphasizes that it swaps the ENTIRE site buyers see. This clearly distinguishes it from sibling publishing tools like publish_shopify_page and publish_shopify_product without needing to open their schemas.

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 condition — 'Use only when the user explicitly approves a full storefront go-live' — and adds approval-rails constraints. It does not explicitly name sibling alternatives or state when-not-to-use, but the condition is unambiguous enough for the agent to route correctly.

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