shopify_create_theme

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

The annotations already signal readOnly=false, idempotent=true, and destructive=true. The description adds valuable behavior beyond those annotations: asynchronous import processing, the required get_theme readback, role restrictions, effect verification, and approval_ref semantics for resuming writes. It does not contradict the 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 compact and well-structured: a front-loaded summary paragraph followed by a clean Args list. Every line adds useful information, and there is minimal padding or repetition.

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?

The description covers the core action, default behavior, async processing, verification requirement, and the unusual approval/effect/idempotency parameters. Since an output schema is present, return values do not need to be described. A small gap is the lack of detail on failure conditions or what happens if the async import fails.

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?

The schema provides 0% description coverage, so the description carries the burden. It explains all nine parameters, including defaults, the only accepted role, idempotency, effect verification, and approval_ref. However, it calls name 'required' in prose while the schema lists it as nullable with no required constraint, creating a minor semantic mismatch.

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 uses a specific verb and resource: 'Create a new DEVELOPMENT theme from a theme zip URL.' It also clarifies the default source and the DEVELOPMENT-only role, distinguishing this create operation from siblings like shopify_update_theme, shopify_duplicate_theme, and shopify_publish_theme.

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 clear operational context: Shopify may process the import asynchronously, and the agent must use get_theme readback before a release cut. It does not explicitly contrast against sibling tools, but the intended scenario and follow-up verification step are clear.

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