Preview Cloudflare Move

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable context by specifying what the preview shows (records copied vs. dropped) and that records are created DNS-only, but it does not mention return format details, auth requirements, or rate limits.

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 sentences, each earning its place: first states the core action and key constraint, second gives usage context, third clarifies a behavioral detail. The purpose is front-loaded and there is no redundant text.

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 a read-only preview tool with a single simple parameter and no output schema, the description adequately covers what is returned, what side effects are avoided, and how the step relates to proxying. Nothing essential for correct invocation 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 description coverage is 100% with one parameter, and the description adds no meaning beyond the schema's 'Domain to preview.' Baseline 3 is appropriate when the schema fully documents the parameter.

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 uses a specific verb ('Show') and resource ('DNS records would be copied into Cloudflare'), and it distinguishes this preview from the actual move by stating 'WITHOUT queueing anything' and from proxying by referencing set_cloudflare_proxy. An agent can immediately tell what this tool does and how it differs from siblings like connect_domains_to_cloudflare.

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 'to tell a user what a move will do to their DNS before committing', and it names set_cloudflare_proxy as the alternative for proxying. These instructions make the when-to-use and when-not-to-use clear without inference.

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