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

The description adds one behavioral fact beyond the schema: 'Page content is not stored,' which is a useful privacy cue. Since no annotations are present, the description still carries the full burden, and it does not clarify network access, error behavior, whether other input fields are ignored, or any side effects. With no annotations, this partial transparency is only moderately adequate.

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 extremely compact, using two short sentences to state the core functionality and a key privacy attribute. There is no filler or redundancy, and the primary behavior is effectively front-loaded.

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 9 optional parameters, no output schema, and a description that mentions only the URL behavior, the definition is incomplete. An agent cannot know what to expect if it passes ref, city, feed, json, host, path, zone, or query, nor how these discarded values relate to the returned host/scheme/status. The description is likely far too narrow for a tool whose schema exposes many other inputs.

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 has 100% description coverage, but each parameter is described individually with 'discarded' language. The tool description does not connect those disparate parameters to its stated core function, nor does it clarify whether the URL parameter is required when other parameters are used. The schema provides the details, and the description adds no parameter-level meaning.

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 deliverable (host, scheme, HTTP status for a URL) and explicitly notes that page content is not stored, which is more concrete than the tool name alone. However, it does not differentiate this tool from siblings like fetch-status, normalize-url, or web-fetch, and the 9-parameter schema hints at a broader purpose the description omits.

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?

The phrase 'for a URL' implies the tool is appropriate when the agent needs host/scheme/status information from a URL. There is no when-not-to-use guidance, no mention of alternative sibling tools, and no indication of how to handle URL normalization or validation before calling. Usage context is only minimally supplied.

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