bind_refresh_zone

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral trait beyond that — "transfer completion remains unknown" warns the operation is asynchronous and unverifiable from the response. It says nothing about required permissions, what gets invalidated, or the dry_run escape hatch.

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 front-loaded sentence with the operation class first and the caveat second — nothing padded. The [WRITE] prefix duplicates annotation information, so it earns no credit but costs almost nothing.

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 zero schema coverage and no output schema, the description is too thin. An agent still doesn't know what target means, how dry_run changes behavior, or what a successful response looks like — all of which the description must supply here.

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%, so the description carries the full burden for zone, target, and dry_run. It clarifies nothing: "secondary zone" loosely implies zone, but target (presumably which server to ask) and dry_run (a preview mode that matters for a destructive write) are completely undocumented in both schema and description.

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?

"Ask a secondary zone to refresh" states a specific verb (refresh) and resource (secondary zone), which an agent can distinguish from bind_retransfer_zone's retransfer semantics. The [WRITE] tag reinforces the mutation nature, though the closest sibling (bind_retransfer_zone) is never named or contrasted.

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 "secondary zone" implicitly scopes when this applies (not for primary/authoritative zones), but there is no explicit when-to-use/when-not guidance and no routing advice versus bind_retransfer_zone or bind_reload_zone. The agent must infer the choice between refresh, retransfer, and reload.

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