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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It discloses that page content is not stored, which is a useful constraint, but it omits other important behaviors implied by the schema, such as 'no disk access' for the path parameter and the fact that many inputs are 'discarded after the check.' It does not mention whether the tool makes network calls for each input type, what happens with invalid inputs, or any authorization/rate-limit implications. The description is too thin to inform an agent about the tool's side effects and constraints.

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 a single sentence, which is concise and front-loaded with the core action. However, it is under-specified relative to the tool's apparent complexity (9 parameters). The brevity is not a virtue here because it omits critical information about the tool's full behavior. It is appropriately short in word count but not in informational completeness, so it does not earn a high score for structure.

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?

Given the tool has 9 optional parameters, no output schema, and no annotations, the description is severely incomplete. It only covers URL-related functionality and ignores the other parameters entirely. An agent would not know how to invoke the tool correctly for non-URL inputs, nor what to expect as output. The absence of output schema and annotations makes the description the only source of context, and it fails to provide adequate guidance.

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 100%, so each parameter is already documented with a short description in the schema. The tool description adds no additional semantic value for the parameters—it only mentions 'URL' generically without specifying that the 'url' parameter is the one used. Given the high schema coverage, a baseline of 3 is appropriate; the description does not enhance parameter understanding beyond the schema.

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 states a specific action (return host, scheme, HTTP status) for a URL, which gives a clear verb and resource. However, the input schema lists 9 parameters with varied purposes (city, feed, json, path, zone, query, etc.) that are not mentioned at all. This creates ambiguity about the tool's actual scope—whether it is exclusively URL-related or handles multiple input types. It partially distinguishes from siblings like 'normalize-url' and 'fetch-status' but does not clarify its relationship to the many shape-check tools in the sibling list.

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 is no guidance on when to use this tool versus alternatives. Sibling tools such as 'normalize-url', 'fetch-status', 'browser-url-ok', and 'validate-json' likely overlap in function, but the description offers no exclusions or conditions. An agent cannot decide whether to pick this tool over a sibling without inspecting their schemas and behavior independently.

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