dohLookup

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

No annotations provided, so the description carries the burden. It describes the action (DNS query) but does not disclose side effects, rate limits, authentication needs, or that it is a read-only operation. The existence of an output schema provides some return value context, but the description itself adds minimal behavioral detail beyond the name.

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?

The description is a concise paragraph followed by a bullet list of use cases. It is front-loaded with the primary purpose, and every sentence adds value. No waste.

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?

Given the tool's simplicity (3 parameters, 1 required) and the presence of an output schema, the description covers the purpose and common use cases. It does not mention error scenarios or prerequisites like having a NextDNS profile configured, but the default profile_id mitigates that. Overall sufficient for a straightforward lookup 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 100%, so the schema already documents all three parameters thoroughly. The description reiterates the profile's purpose but does not add new semantic meaning to the parameters beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool performs a DNS-over-HTTPS lookup using a NextDNS profile, with specific verb and resource. It distinguishes from sibling tools which are mostly about managing blocklists, allowlists, analytics, etc. The use cases list adds clarity.

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 description explains when to use the tool: testing domain blocking, verifying resolution, debugging, and testing allowlist/denylist. It does not explicitly state when not to use it or name alternatives, but the context and sibling list make it clear this is the only DNS lookup tool.

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