bind_diagnose_zone

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds that multiple probes are combined and only failures are reported. Beyond that it says nothing about latency (five probes could be slow), whether probes hit live servers, or what happens when a probe errors rather than fails. For a multi-step diagnostic this is thin.

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 [READ] marker up front and zero filler. It is efficient, though the semicolon-clause format leaves the most important detail, what a report actually contains, compressed into three words.

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?

With no output schema and two undocumented parameters, the description should explain the shape of the failure report and how 'target' changes behavior; it does neither. An agent knows roughly what the tool is for but not how to call it correctly or what it will get back.

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 and adds nothing: it never explains whether 'zone' expects a fully qualified name with trailing dot or a view-qualified form, nor what 'target' means (a specific server to direct probes at versus the default). Both parameters are undocumented in both places.

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 verb and resource: it correlates named, config, zone, SOA and DNSSEC probes and reports failures. That distinguishes it from single-probe siblings such as bind_config_check, bind_compare_soa, and bind_dnssec_validation, though it does not name those siblings explicitly.

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?

Usage is only implied: the list of probes it aggregates suggests this is the combined-diagnosis entry point rather than one of the single-probe siblings. There is no explicit when-to-use statement, no guidance on when a single probe would suffice, and no prerequisites such as the need for a resolvable zone.

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