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

Annotations already declare idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond the structured fields: publishing is free on every plan, free sites get a JustCopy badge, and republishing mutates the live site rather than creating a duplicate. It omits auth/permission requirements, which is the only notable gap.

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 short sentences, front-loaded with the core action, then cost/badge, then the optional address format and republish behavior. No sentence is redundant against the schema or annotations.

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?

An output schema exists, so return values need no explanation. The description covers cost, badge exposure, subdomain semantics, and repeat-publish behavior, which is nearly everything an agent needs. Only permission/authentication expectations are absent.

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 baseline is 3, but the description earns extra credit by giving the fully resolved host form (<address>.app.justcopy.ai) and the accepted character set, which the schema's regex pattern does not spell out in words. The siteId parameter is left to the schema, which already points at list_sites or create_site.

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 and resource — 'Puts a built website online at a public link' — and the phrase 'a built website' implicitly separates it from the create_site sibling, which does not imply a pre-existing build artifact. An agent can distinguish publishing from creating or fetching a site without opening another 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?

Usage is only implied: 'Publishing again updates the live site' tells the agent this is repeatable, but no sibling is named and no condition is given for choosing publish_site over change_site or get_site. The guidance is adequate but stops short of explicit when/when-not routing.

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