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

With no annotations, the description carries the full burden and does well: it discloses that NessGate reads the domain live, stores nothing, adds no ownership/safety claim, and that each returned resource carries a sourceUrl for verification. This is meaningful behavioral context, though it omits failure behavior (what happens when a domain publishes none of these) and any rate-limit or timeout information.

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?

Front-loaded with the core action and input, then the endpoint list, then trust/verification caveats. The long enumeration is informative rather than filler, though it is somewhat dense for three sentences.

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 no output schema, the description usefully sketches the return contract ('one normalized answer', per-resource sourceUrl) and states the live/no-storage behavior. Missing only edge-case handling and any indication of result size or shape when discovery yields little.

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% and the single 'domain' parameter is fully documented in the schema, so the baseline is 3. The description adds only 'Given a domain', with no extra format or validation detail (e.g. subdomain handling) beyond the schema's registrable-domain clarification.

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?

States a specific verb+resource (read a domain's published machine-discovery resources) and enumerates the exact locations checked (llms.txt, /.well-known/ard.json, agent-card.json, api-catalog, openapi.json), leaving no ambiguity about what it does. An agent can immediately tell this resolves a domain's metadata rather than, say, fetching a URL or calling an API.

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?

There are no sibling tools, but the description only implies the trigger (resolve what a domain publishes) rather than stating when to reach for this versus other approaches. It never says when not to use it or what scenario makes it the right first step.

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