bind_zone_status

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

The read-only claim is consistent with readOnlyHint=true, and "live zonestatus" adds the useful nuance that this reports runtime state. It says nothing about what happens if the zone is not loaded, what the status covers, or how the `target` parameter changes behavior.

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 zero padding. It is tight, though the brevity is achieved by omitting content rather than by disciplined editing.

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?

This is a simple read tool with no output schema, but with 0% schema coverage and an undocumented `target` parameter, the description leaves real gaps. A status call typically returns serial, expiry timers, and load state, and none of that is hinted at.

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 one zone" loosely anchors the required `zone` parameter but adds no format or naming guidance, and the optional `target` parameter is not mentioned at all.

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: get BIND's live zone status for one zone. The word "live" usefully signals runtime state rather than config, which helps separate it from siblings like bind_show_zone. It never names an alternative outright, so the differentiation is inferential.

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 "[READ]" tag marks it as non-mutating, but there is no statement of when to prefer this over bind_status, bind_show_zone, bind_dnssec_zone_status, or bind_managed_keys_status. The agent must guess from the name alone.

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