dig

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

Description only states 'Perform DNS lookup', adding no behavioral details beyond the action. Annotations indicate readOnlyHint=false, but the operation is inherently read-only, creating a potential mismatch. No disclosure of side effects, permissions, or output characteristics.

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?

Single sentence with no filler, directly conveying the tool's purpose. Excellent conciseness.

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?

Simple tool with well-described parameters, but no output schema or description of the result format. Given the complexity, the description is minimally adequate but would benefit from mentioning typical dig output (e.g., IP addresses, record details).

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?

Input schema provides 100% description coverage for both parameters (target and type). The description adds no extra meaning beyond what the schema already conveys, so baseline score of 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?

Description clearly states 'Perform DNS lookup' with a specific verb (Perform) and resource (DNS lookup). The tool name 'dig' is a well-known command, making purpose clear. However, it does not differentiate from sibling tool 'nslookup' which also 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?

No guidance on when to use this tool versus alternatives like nslookup, ping, or curl. Lacks context about prerequisites or typical use cases.

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