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

With no annotations, the description carries the transparency burden. It does disclose one meaningful trait, 'Page content is not stored,' but it does not mention whether a live network request is made, how errors are surfaced, or any rate or auth considerations.

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 sentences with no filler; the core outcome is front-loaded and the storage disclaimer earns its place as a safety note.

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?

For a tool with nine optional parameters and no output schema, this description is too thin: it does not state which parameter to supply or what happens for invalid or non-HTTPS URLs, and the many unrelated-looking schema parameters are left unexplained.

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 schema descriptions already cover all parameters, giving a baseline of 3. The description confirms the url parameter is the focus but adds no value for the many other optional parameters, leaving ambiguity about how they relate to the core URL operation.

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 names a concrete operation and resource: return host, scheme, and HTTP status for a URL. It is specific enough to distinguish from normalizing or fetching page content, though it does not explicitly name a sibling tool to differentiate itself from.

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 about when to choose this tool over siblings such as web-fetch, normalize-url, or fetch-status. The only extra sentence is a storage disclaimer, not a usage condition.

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