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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states the core action and does not mention that this likely performs a live network query, what record types are supported, whether failures or timeouts can occur, or any output characteristics. This leaves the agent without insight into side effects or environmental dependencies.

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, front-loaded sentence with no redundant filler. It immediately states the action and target, which is the appropriate level of brevity for a simple lookup tool.

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 absence of annotations, an output schema, and parameter descriptions, the description is too thin to fully support correct invocation. It does not explain valid record_type values, the expected domain format, what the response contains, or when this tool should be chosen over a sibling. The agent would need to rely on assumptions beyond the provided definition.

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 input schema provides only titles and a default value, with 0% schema description coverage. The description does not compensate by explaining what 'domain' should look like or which values are valid for 'record_type'. The phrase 'DNS records' hints at record types, but the agent is left guessing about supported types such as A, AAAA, MX, or TXT.

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 identifies a specific operation ('Resolve DNS records') and a target ('for a domain'), which is enough to distinguish it from the sibling lookups like get_ssl_check or get_security_headers. However, it is terse and does not explicitly mention the configurable record type or differentiate itself from broader domain tools such as get_domain_intelligence.

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 usage guidance is provided. The description does not state when to use this tool instead of related options like get_domain_intelligence or get_security_posture, nor does it give any context about typical use cases such as checking DNS configuration or troubleshooting resolution. The intent is only implied by the tool name and the verb 'Resolve'.

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