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

Adds real behavioral context beyond the annotations: the original site is not modified, the copy is unpublished, and every call produces yet another copy (no idempotency). That last point is exactly the kind of trait annotations cannot express. It omits auth/permission requirements.

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?

Front-loads the use case, then the effect, then the repeat-call caveat. The dashboard analogy ('the way Duplicate does on the WebTwizz dashboard') is mildly expendable but the rest earns its place.

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?

With no annotations about returns and no output schema, the description should say what the agent gets back — critically, the new site's ID needed to publish or edit the copy. It covers what happens to the original but not how to use the result, leaving a real gap for a creation tool.

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 50%: name is documented in the schema (including the '<original name> (Copy)' default), while site_id is undocumented. The description adds no parameter-level detail (e.g., that site_id is the source to copy), so it neither compensates for nor undermines the schema.

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 specific verb (duplicate/copy) and resource (WebTwizz site), then clarifies the resulting artifact: a new, unpublished project with the same pages, design and content. This distinguishes it from create-site (blank site) and from update-site without needing the schema.

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?

Gives clear when-to-use contexts: copying to try ideas without touching the original, or starting a similar site. It does not explicitly name an alternative tool (e.g., create-site) or state when-not-to-use, so it stops short of full routing guidance.

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