bind_query

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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It does add one useful trait: the tool surfaces the server's *actual* response code rather than masking it, which hints that NXDOMAIN/SERVFAIL are returned as data rather than errors. It says nothing about timeouts, whether the query recurses, or what the response payload contains.

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 no filler. The [READ] tag partially duplicates readOnlyHint, but the sentence itself is tight and the key behaviour (exposing the real response code) is not buried.

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 small three-parameter lookup tool with annotations covering safety, the description covers the core action. But with 0% schema coverage and no output schema, the roles of rrtype and especially target (which server is actually queried) are left undocumented, which is a real gap for a diagnostic tool.

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 three parameters — name, rrtype (default A), and target (nullable, default null) — and explains none of them. 'Configured DNS server' weakly implies target overrides the server, but this is guesswork rather than stated semantics.

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: query the configured DNS server and expose its response code, with a [READ] prefix signalling a non-mutating lookup. It does not, however, distinguish itself from the very similar sibling bind_query_server, which an agent cannot disambiguate from this text alone.

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 or when-not-to-use guidance. With a near-identical sibling (bind_query_server) and related tools like bind_diagnose_zone and bind_flush_name in the list, the description leaves selection entirely to inference.

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