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

Annotations already mark this destructive and non-idempotent, and the description adds substantial context beyond them: the published copy stays live until a separate publication, sibling routes are untouched, the operation is asynchronous and must be polled via get_agent_session, source edits may execute in its preview, and the agent may use connected integrations. That is real behavioral disclosure, not a restatement of the hints.

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 critical constraints (what is removed, what survives, async polling) are front-loaded, which is good. However the tail sentence about the Replo agent using its normal tools and integrations is generic boilerplate that does not help an agent decide or invoke, and the description sprawls across eight sentences.

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, destructive, session-based mutation with no output schema, the description covers everything needed: prerequisite (provisioned site), return-handling (poll get_agent_session), correction flow, blast radius, and the separate publish step. Nothing an agent needs to invoke correctly is missing.

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 baseline is 3, but the description adds usage semantics the schema only implies: the sessionId is for continuing/correcting an operation and must target the same route. The instructions parameter's content restrictions are already fully covered by the schema.

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 ('Remove the selected route's draft page') and immediately bounds scope by negation: it does not delete the site or other routes, and it does not publish. An agent can separate this from edit_site_page, create_site_page, and publish_site without opening a 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?

Gives explicit routing guidance: use publish_site separately to make changes public, requires a provisioned site, and describes the correction path (re-call with sessionId and unchanged target). It stops short of explicitly contrasting with edit_site_page for the 'change rather than remove' case, so no exclusion is stated.

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