dohLookup

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

No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. It states the tool performs a network lookup, implying potential latency and internet dependency, but fails to mention side effects (likely none), required authentication (NextDNS profile), rate limits, or that the operation is read-only. This is insufficient for an agent to understand the tool's behavior.

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 single, concise sentence that captures the tool's core function without any unnecessary words or redundancy. It is well-structured and front-loaded, making it easy for an agent to quickly grasp the 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?

With three parameters and an existing output schema, the description is minimally adequate. It provides the essential action but omits context about when to call this tool (e.g., for DNS resolution with NextDNS privacy), typical use cases, or expectations about return values. The presence of an output schema reduces the burden, but the description still lacks sufficient context for a complete understanding.

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%, so the baseline is 3. The description does not add any additional meaning or context to the parameters beyond what the input schema provides. For instance, it does not explain the relationship between domain and profile_id, nor the significance of the default record type. No extra value is contributed.

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 uses the verb 'Perform' and specifies the resource 'DNS-over-HTTPS lookup' with the context 'using a NextDNS profile.' It clearly communicates the core action and resource, though it does not explicitly distinguish from sibling tools like manageLists or plotAnalytics. The distinction is implicit given the tool name and focus on 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 no guidance on when to use this tool versus alternatives, nor does it mention when not to use it or what prerequisites are needed (e.g., internet connectivity, NextDNS API access). This leaves the agent without context for tool selection.

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