bind_query_server

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

The '[READ]' prefix merely restates readOnlyHint=true. With annotations carrying the safety profile the bar is lower, but nothing is said about timeout behavior, what happens when the target server is unreachable or non-authoritative, or recursion/EDNS behavior — meaningful context for a network query tool.

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 wasted wording; the [READ] tag is mildly redundant with the annotation but still aids scanning.

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?

Four parameters with zero schema descriptions, no output schema, and an ambiguous nullable 'target' argument — the description does far too little to make this callable correctly given the complexity and sibling density.

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 must compensate and it largely does not: 'record type' maps to rrtype and 'specified DNS server' maps to server, but the meaning of 'name' (query name?) and especially 'target' (nullable, default null) is left entirely unexplained.

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?

Specific verb+resource: query a DNS server for a supported record type. The word 'specified' hints at the distinction from the sibling bind_query (presumably local/default server), but it never names that sibling or states the boundary 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 by 'a specified DNS server' — an agent can infer this is for querying an arbitrary/external server rather than the local one, but there is no explicit when-to-use, when-not, or named alternative among the many bind_* siblings.

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