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

Annotations cover the safety profile (non-read-only, destructive, non-idempotent, open-world), and the description adds substantive context beyond them: it is an asynchronous internal-agent operation requiring polling, it needs a provisioned site, source edits may execute in the preview, and changes are not public until publish_site runs. These are exactly the operational traits an agent needs and are not present in structured fields.

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 concrete update scope, followed by operational behavior and routing. Mostly earns its place, though 'The Replo agent uses its normal tools and connected integrations to implement and verify the requested changes' is somewhat vague and adds little actionable information.

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?

There is no output schema, and the description compensates by explaining the async session model, polling, correction flow, provisioning requirement, and preview/publish semantics. An agent has everything needed to invoke it correctly and follow up.

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 meaning on top: sessionId is for continuation/corrections with an unchanged target, and instructions should carry references rather than conversation history or credentials. This clarifies the sessionId workflow beyond the schema text.

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 precise verb and the exact resource surface: site-wide SEO title, description, social preview, favicon references, and search visibility in the root layout. It also carves out what it does NOT do ('Does not rename the dashboard label') and points to publish_site, so an agent can distinguish it from sibling update tools.

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?

Explicit routing is given: poll get_agent_session after starting, re-invoke this same tool with sessionId for corrections, and use publish_site separately to make changes public. Prerequisite ('Requires a provisioned site') is stated. This is close to a complete when/when-not/alternatives map.

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