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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds value by disclosing the exact output components – answer, flags, rcode, Extended DNS Errors, latency, dig-style text, and JSON – which is especially useful given there is no output schema. There is no contradiction with annotations.

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 well-formed sentence front-loads the action and then lists the return payload, with no redundant or filler phrases. It is dense without losing clarity.

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?

Fully documented parameters, robust safety annotations, and an output-shape summary together make the tool easy to invoke correctly. The absence of an output schema is compensated by the description's explicit mention of the dig-style response plus JSON, so nothing critical is missing.

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 100%, and each of the 10 parameters has descriptive text with defaults, enums, and examples, so the schema carries the semantic load. The description adds no parameter-level meaning beyond what the schema already provides, which is acceptable at the baseline.

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 states a concrete action ('Ask ... for a record') on a specific resource (a public DNS resolver or any public address), and the output description ('in the shape dig prints, plus the JSON') clearly differentiates it from sibling tools like check_domain or dns_events. It is not a tautology and leaves no ambiguity about what operation is performed.

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 'live, from the isitdns seat' implies this tool is for current DNS lookups, but the description never explicitly says when to prefer it over sibling tools or when not to use it. No alternatives are named, so the agent must infer use cases from the schema and sibling names.

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