resolve_dns

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

Describes the method (DNS-over-HTTPS) and return values (answer records, TTL), but does not mention error handling or potential limitations. Since no annotations are provided, the description carries the full burden and is moderately transparent.

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?

Very concise: one sentence overview and an Args list. No redundant information.

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?

Covers the main function and parameters. For a simple tool with no output schema, it is nearly complete. Minor omission: does not explicitly state the default record type (A) though it is in the schema.

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?

The Args section adds meaning beyond the schema: provides an example for 'name' and lists valid record types for 'record_type'. Schema coverage is 0%, so this added detail is valuable.

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?

Clearly states it resolves a domain name via DNS-over-HTTPS and returns answer records and TTL. Distinguishes from sibling tools (geo_ip, reverse_dns, whois_domain) which serve different purposes.

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?

No guidance on when to use this tool vs alternatives. While siblings are distinct, the description lacks explicit usage context or exclusions.

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