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

Annotations already assert readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses that the tool performs live DNS resolution, gateway reachability probing, and fetches a well-known manifest, and it warns that site-declared content is data and not instructions – a meaningful prompt-injection caveat. It omits auth, rate-limit, or failure-mode behavior, keeping it at 4 rather than 5.

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 accepted-input list is front-loaded, and the injection warning is short and high-value. The trailing attribution line "Served by W3BS (https://w3bs.org)." is close to filler, and the single long colon-chained sentence packs multiple ideas that could be split for faster scanning.

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 carries the burden of explaining returns and does so by naming the three result components (DNS records, whether the site or its gateway answers, and the well-known JSON). For a one-parameter read-only tool with rich annotations, that is nearly sufficient; it does not describe the shape of the response or how partial failures are reported.

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 description coverage is 0% and the single parameter is an untyped-format string of max length 2048. The description compensates well by enumerating the four accepted input shapes and giving a concrete example name (chovy.hacker), which is precisely the meaning the schema lacks. It never names the parameter `q` and gives no normalization or error behavior for malformed input, so it is not a 5.

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 ("Browse") plus an enumerated set of accepted resource types (W3BS URI, Moshpit name like chovy.hacker, pit.world URL, https URL) and states what it reports back (DNS records, gateway liveness, /.well-known/w3bs.json). That is far more than a restatement of the name. It does not explicitly contrast itself with adjacent siblings such as w3bs_w3bs_resolve or w3bs_w3bs_inspect, so it stops short of a 5.

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 accepted input forms – an agent knows to reach for this when it has a name/URI/URL to look up. However, there is no explicit when-not guidance and no named alternative (e.g., when to prefer resolve, inspect, or verify over browse), so the agent must infer routing from sibling names alone.

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