create_site_from_template

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

With no annotations, the description carries the behavioral burden. It discloses that the tool clones the template's pages, global sections, cart, popups, styles and fonts, and that it switches the session to the new site—a key side effect. It implies the new site is not yet published by directing next steps to publish_site, which is useful disclosure, though return values and error cases are not mentioned.

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 three sentences, each earning its place: what it does, what it clones, and how to use it next. It is front-loaded with the core purpose and avoids filler.

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?

Even without annotations or an output schema, the description provides a complete operational picture: prerequisites, cloned content, session switching, and next steps for editing and publishing. This is sufficient for an agent to select and invoke the tool 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?

All four parameters are already described in the schema (100% coverage), so the baseline is 3. The description adds meaningful workflow context by explaining where theme_id comes from (semantic_search_themes/list_template_themes) and confirming the switch_to behavior, which helps an agent correctly construct the invocation.

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 opening sentence states a specific action ('Create a NEW site from a marketplace TEMPLATE') and designates it as the dedicated API, distinguishing it from the sibling create_site. It also names the cloned resources (pages, global sections, cart, popups, styles, fonts), making the tool's role unmistakable.

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 provides a concrete workflow: pick a template with semantic_search_themes/list_template_themes, pass its theme_id, then edit with update_page_element(s)/site-style tools and publish_site. This explicitly frames the prerequisite and follow-up actions, and the 'dedicated API' wording subtly distinguishes it from create_site.

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