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

With no annotations, the description carries the full burden and does well: it discloses the 15-asset cap, that only same-site CSS/JS are pulled, that references are rewritten, and that each call costs 3 credits. It omits auth/permission requirements and what happens on partial or failed imports of large pages.

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 sentences, front-loaded with the core action, followed by the workflow and the constraints/cost. No filler and nothing buried.

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?

Covers purpose, asset scope, reference rewriting, ownership constraint, and credit cost despite having no annotations and no output schema. It could say more about auth requirements, failure modes, and the site_id-vs-new-workspace choice, but an agent has enough to invoke it 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?

Schema description coverage is only 33% (only site_id is documented), so the description should compensate more than it does. It implies the url is the public page being copied and hints at workspace creation/deployment, but says nothing about the 'name' parameter and never explains importing into an existing workspace via site_id.

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 ('copy') and resource ('a public page and its same-site CSS and JavaScript') and names the resulting target ('new editable workspace'). It also differentiates itself from crawler/scraper siblings like crawl_site and scrape_page by making clear the output is an editable local copy with rewritten references.

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 a concrete workflow ('fix the code with site_files and site_autofix, then publish a corrected version') plus an explicit precondition ('Only import sites your customer owns or has asked you to fix'). It does not contrast with the nearest alternatives (crawl_site, scrape_page, site_create), so it falls short of a full when/when-not statement.

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