create_site_from_template

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

Adds real behavioral context beyond the annotations: it discloses exactly what content is cloned into the fresh site and that the session switches to the new site so you can edit immediately. This is consistent with readOnlyHint=false / destructiveHint=false (additive, non-destructive creation) and enriches the picture.

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?

Three tightly written sentences, front-loaded with the core action, then prerequisites, then follow-on workflow. No filler; the cloning list is informative rather than redundant.

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 4-param, no-output-schema mutation tool with annotations present, the description covers prerequisites, side effects, and next steps. It could be slightly richer on what the call returns (e.g., the new site id), but it is well-rounded for correct invocation.

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 coverage is 100%, so the schema already documents name, slug, theme_id, and switch_to. The description reinforces theme_id's source and the switch behavior but adds little syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a precise verb+resource (create a NEW site from a marketplace TEMPLATE) and explicitly notes it is the dedicated 'use this template' API, distinguishing it from the sibling create_site. The cloning scope (pages, global sections, cart, popups, styles, fonts) makes the behavior concrete.

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?

Clearly names the prerequisite discovery tools (semantic_search_themes / list_template_themes) and the ordering ('pick a template ... then pass its theme_id here'), plus follow-on steps (update_page_element(s), site-style tools, publish_site). It doesn't explicitly contrast with create_site for a blank site, so an explicit when-not is missing.

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