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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavioral context: the call fans out in parallel to three DoH resolvers, and it costs $0.01 USDC per successful call via x402 on Solana, with an equivalent HTTPS endpoint. It does not describe failure behavior (what happens when a resolver times out or the payment fails).

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?

Two compact sentences plus a price/endpoint line, with the core capability front-loaded and the commercial detail trailing. Slightly dense but nothing repeated and nothing wasted.

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?

No output schema exists, and the description compensates by naming the return contents (consensus, per-resolver answers, TTLs, rcodes, differences), plus cost and an alternate endpoint. Missing only failure/timeout semantics and payment-failure handling for a paid, multi-resolver call.

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% with enums and defaults already documented, so the schema does the heavy lifting. The description only restates the core semantics ('resolves one record type', three resolvers in parallel) without adding format, syntax hint, or edge-case guidance for domain IDN handling or the resolvers subset.

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 gives a specific verb and resource — resolves one record type for a domain across three named resolvers — plus the transport (DNS-over-HTTPS, parallel) and the returned consensus data. It's clear enough to call without opening the schema, but it never positions itself relative to close siblings like dns_dump or mx_check, so an agent must infer the boundary.

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?

Usage is implied by the phrase 'DNS propagation check' and the multi-resolver scope: use it when you want cross-resolver agreement. There is no explicit when-to-use/when-not, no mention of prerequisites (e.g., only one record type per call), and no named alternatives such as dns_dump for full records or mx_check for mail config.

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