bind_reload_zone

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

Annotations already declare a non-read-only, non-idempotent, destructive write. The description adds genuinely new context beyond them: the reload is queued rather than executed synchronously, and completion remains unknown. That is exactly the kind of async/fire-and-forget caveat an agent needs. It still omits whether the zone is interrupted and whether config validation failures abort the queue.

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 tight sentence with the operation class front-loaded and no filler. The brevity is appropriate in form even though it leaves gaps that other dimensions penalize.

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 mutation with three parameters at 0% schema coverage and no output schema, this is too thin. An agent gets no information about the target parameter, how to invoke safely, or what a queued result looks like.

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 communicates almost nothing about the three parameters. 'zone' is inferable from 'zone reload', but 'target' (presumably a view or server selector) and 'dry_run' are left entirely undefined, and the text never hints that a dry-run mode exists.

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?

States a specific verb and resource: it checks configuration and queues a zone reload. The '[WRITE]' prefix immediately signals the operation class. It does not distinguish itself from siblings like bind_refresh_zone or bind_retransfer_zone, which sound adjacent.

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 explicit when-to-use guidance and no mention of when not to use it. Several siblings (bind_refresh_zone, bind_retransfer_zone, bind_notify_zone) plausibly overlap, and the description gives an agent nothing to choose between them.

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