dohLookup

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

No annotations are provided, so the description carries the full burden. It discloses that the tool performs a DNS query via NextDNS's DoH endpoint, which is read-only and non-destructive. It does not mention rate limits or auth requirements, but for a simple query tool, the behavioral transparency is sufficient.

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 concise with a clear opening sentence and bulleted use cases. Every sentence adds value without redundancy. Front-loaded with purpose.

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, output schema exists, and no annotations are needed. The description covers purpose, usage, parameters, and use cases completely. No gaps.

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 coverage is 100%, and the description adds significant value beyond the schema: example domain format, explanation of profile_id default, and a comprehensive list of record types with usage context. This helps the agent select correct parameter values.

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 'Perform a DNS-over-HTTPS lookup using a NextDNS profile' with specific verb and resource, and lists concrete use cases like testing blocked domains and debugging. It distinguishes itself from siblings as no other sibling performs DNS lookups.

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 provides explicit use cases (testing blocked domains, verifying resolution, debugging, testing allowlist/denylist). While it does not include explicit when-not-to-use or alternative tools, the context is clear and the intended scenarios are well-defined.

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