migrate_import_dns_zone

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

With no annotations, the description bears the full burden of explaining behavioral traits. It mentions the environment variable requirement, which is useful, but it does not disclose whether the import is destructive, whether it replaces an existing zone, whether it is idempotent, or what side effects occur on the destination instance. This is a notable gap for an import operation that clearly writes state.

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 description is a single, efficient sentence that front-loads the core purpose and includes a key prerequisite. There is no redundant or low-value text. While it is terse, it avoids any filler and remains focused.

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 state-changing import tool with no output schema and no annotations, the description is incomplete. It does not explain what happens after a successful import, how conflicts are handled, or what the return value represents. The destination server requirement and the source of the bundle are implied but not explicitly connected in the description.

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%, so the baseline is 3. The schema already documents bundle_json, dest_client_id, and dest_server_id with meaningful descriptions. The tool description does not add additional parameter-level nuance beyond what the schema provides.

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 action ('Import'), the resource ('DNS zone migration bundle'), and the target ('destination ISPConfig instance'). This clearly distinguishes it from the sibling migrate_import_mail_domain and migrate_import_web_domain tools. The phrase 'from migrate_export_dns_zone' in the schema further reinforces the exact resource type.

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 description gives one precondition ('Requires ISPCONFIG_DEST_URL to be configured') but provides no guidance on when to choose this tool over alternatives. It does not state that this is part of a migration workflow or that it should be used after migrate_export_dns_zone. The usage context must be inferred from the tool name and sibling tools.

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