bind_retransfer_zone

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

The annotations already declare a destructive, non-idempotent write. The description adds useful context with 'completion remains unknown', warning that the operation is asynchronous or indeterminate, but it does not explain what is overwritten, required permissions, or how to verify completion.

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 compact sentence that front-loads the write marker and includes the key outcome caveat. There is no filler or repetition beyond the bracketed write tag.

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, non-idempotent, three-parameter mutation with no output schema and zero schema descriptions, the definition omits prerequisites, target semantics, dry_run behavior, and verification guidance. It covers purpose and indeterminacy but is not complete enough for safe invocation.

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 0%, and the description does not define zone, target, or dry_run. 'Secondary zone retransfer' weakly implies the zone parameter, but target and dry_run remain semantically opaque, so the description does not compensate for the schema gap.

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: 'Request a secondary zone retransfer'. It does not distinguish this operation from sibling tools such as bind_refresh_zone or bind_notify_zone, so sibling differentiation is missing.

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?

There is no guidance on when to use this tool versus alternatives like bind_refresh_zone, bind_notify_zone, or bind_show_zone. It also gives no conditions for choosing the optional dry_run or target parameters.

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