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

Annotations already declare destructive=true, idempotent=false, openWorld=true, but the description goes well beyond them: asynchronous internal-agent execution, polling requirement, shared-component edits affecting other pages, execution within the preview, and the correction workflow. This is meaningful side-effect and lifecycle context an agent needs.

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-loaded with the core action and scope, then the async/correction/publish mechanics. Dense and largely waste-free, though the sentence about the Replo agent's normal tools and integrations is somewhat procedural filler relative to the actionable guidance.

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 an async mutation with no output schema, it covers prerequisites, lifecycle (poll get_agent_session), side effects (shared components), and the follow-up publish step. The only minor gap is not describing what the initial invocation returns, though the polling pointer largely compensates.

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 100%, so the baseline is 3, but the description adds real semantics: sessionId is omitted to start and supplied with an unchanged target to continue, and mismatches are rejected. That workflow meaning for sessionId exceeds a bare field description.

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 (Edit) and resource (the selected site's draft page at one route), then enumerates the editable surface: copy, sections, product display, forms, page-local components. This clearly distinguishes it from siblings like create_site_page, delete_site_page, update_site, and update_site_metadata.

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?

Explicitly names the alternatives and the conditions selecting them: poll get_agent_session for progress, use publish_site separately to go public, and re-call this tool with sessionId for corrections. It also states the precondition (requires a provisioned site), leaving nothing to inference.

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