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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety bar is lower. The description adds useful context — that it is free, that it points DNS at a redirect service, and what preserve_path does — but it does not state what existing DNS records or forwards get replaced, which is the core destructive behavior.

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?

One dense but front-loaded sentence plus a short preserve_path note; nothing is padding. It is slightly run-on, but every clause carries 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?

For a destructive, open-world mutation with no output schema and partial param coverage, the description covers cost, target format, and scope but omits what state is overwritten and what happens on existing competing forwards or DNS records.

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 only 40%, so the description must compensate; it does explain subdomain scope ('@' also covers www), target as an https URL, and preserve_path (/path?query). However, the 'code' parameter is never explained and 'FREE 301' actively suggests only 301 exists despite the enum offering 302.

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 ('forward the whole domain or a subdomain') plus the mechanism ('Points DNS at our redirect service'). An agent can tell exactly what happens to the domain, though it doesn't name a sibling tool to contrast with (e.g. set_dns or list_url_forwards).

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 implies usage context with 'a domain you registered with us', which is a prerequisite, but never says when to choose this over set_dns or how it interacts with existing forwards. No exclusions or alternatives are given.

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