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

The description adds substantial behavior beyond the annotations: the preview is token-protected, the URL works for 60 minutes, the live production version is not affected, and custom primary URLs may be used with a managed fallback. These details are exactly what an agent needs to set expectations and avoid mistaking preview for publication.

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 front-loaded with the core action and then layers in timing, safety, URL behavior, and next steps without wasted text. Each sentence contributes useful operational context.

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 output schema, the description carries the return-value context itself by explaining the tokenized URL, 60-minute lifetime, custom URL path behavior, and fallback URL. Combined with the annotations, it gives an agent enough information to call the tool correctly and interpret the result.

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 both parameters are already documented in the schema. The description repeats that omitting versionNumber uses the latest saved version, but it does not add syntax or format details beyond the schema, so the baseline of 3 is appropriate.

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 description states a specific verb and resource: generate a shareable preview URL for a landing page before going live. It clearly distinguishes the preview from the live production version and from publish_site, but it does not mention the sibling create_landing_page_preview, so sibling differentiation is incomplete.

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?

It explicitly says to use this after save_page_content so the user can review before publishing, and it names publish_site as the next step when the user is happy. It also explains that calling create_preview again produces a fresh link and that publishing is required to show the page to other people.

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