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

Without annotations, the description carries full burden for behavioral disclosure. It indicates a read operation ('resolution') and mentions the external service (Cloudflare DoH), but does not disclose rate limits, caching behavior, error handling, or return format.

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 extremely concise (two words plus provider info) and to the point. It could benefit from slightly more structure or bullet points, but it's efficient.

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?

For a simple tool with no output schema and minimal parameter documentation, the description is insufficient. It lacks details on what the tool returns (e.g., IP addresses, records array) and how to interpret results.

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 schema has no descriptions for parameters 'domain' and 'type'. The description does not explain that 'type' likely refers to DNS record type (e.g., A, AAAA). With 0% schema description coverage, the description fails to add meaning beyond parameter names.

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 'DNS resolution via Cloudflare DoH' clearly states the tool's purpose: performing DNS lookups using Cloudflare's DNS-over-HTTPS service. It distinguishes itself from sibling tools, none of which are DNS-related.

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 is provided on when to use this tool vs alternatives, or any prerequisites or limitations (e.g., Cloudflare DoH restrictions). The agent receives no context for optimal usage.

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