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

The description discloses that page content is not stored, but it does not explain how the many optional parameters (e.g., city, zone, query) are handled beyond the schema notes saying they are discarded. With no annotations provided, this minimal disclosure leaves uncertainty about side effects, network behavior, or why those parameters exist.

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 concise, using two short sentences to convey the core behavior and a constraint. Every sentence adds value, and there is no unnecessary detail or repetition.

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?

The description lacks context about the output format (how host, scheme, and HTTP status are returned), error handling, and the role of the eight optional parameters that seem unrelated to the stated purpose. Given the complexity of the input schema, the description is insufficient for an agent to fully understand the tool's behavior or when to use it.

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 descriptions for all parameters (100% coverage), including those marked as discarded, so the baseline is 3. However, the description itself does not add meaning to these parameters; it only mentions the URL. The schema descriptions supply the discard behavior, but the description fails to clarify the purpose of the extraneous parameters or how they relate to the core function.

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 states that the tool returns host, scheme, and HTTP status for a URL, and explicitly notes that page content is not stored. This specific verb+resource combination distinguishes it from siblings like web-fetch (which fetches content) or fetch-status (which might have different semantics).

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 versus alternatives such as normalize-url or fetch-status. The description does not mention conditions, exclusions, or when a different sibling would be more appropriate.

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