migrate_export_web_domain

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

With no annotations provided, the description carries the behavioral disclosure burden. 'Export' suggests a non-destructive read operation and the listed contents show scope, but the description does not state whether export modifies anything, how the bundle is delivered, or any security/caveat beyond the schema's include_secrets flag.

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?

A single, dense sentence conveys the core purpose and contents with no filler. Every element in the description contributes to understanding what the tool does.

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?

The description is largely complete for invoking the tool: it names the resource, required contents, and export intent, and all parameters are fully documented in the schema. However, there is no output schema and the description only vaguely implies the return mechanism ('as a migration bundle'), leaving delivery/format details underexplained.

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?

The input schema already documents both parameters with 100% coverage, so the baseline is 3. The description adds no additional parameter-level meaning beyond what the schema provides; it does not explain domain_id or include_secrets any further.

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 names a specific verb ('Export') and a specific resource ('a web domain') and enumerates included components (FTP users, shell users, databases, cron jobs, subdomains). It is immediately distinguishable from sibling migration exports like migrate_export_dns_zone and migrate_export_mail_domain.

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?

The phrase 'as a migration bundle' makes the intended context clear, and the resource scope (web domain with associated items) implies this is for full web-domain migration. It does not explicitly mention alternatives or exclusions, so it stops short of perfect guidance.

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