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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that page content is not stored, which is a useful privacy note, but it does not mention whether network requests are made, whether the operation is read-only, or any side effects. The tool's schema includes many parameters that are 'discarded' after checks, but the description gives no context for these, leaving significant behavioral ambiguity.

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 two sentences with no wasted words. The primary function is front-loaded in the first sentence, and the second sentence provides a concise behavioral note. It is appropriately sized and efficiently structured.

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 tool has 9 parameters, no output schema, and no annotations, yet the description only addresses a URL-centric function. It does not explain the purpose of the many other parameters (city, feed, json, path, etc.), nor does it describe the return format or any prerequisites. For a tool with such complexity, this description is incomplete and leaves the agent without sufficient context to use it correctly.

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 description coverage is 100%, so each parameter is already documented with its own description. The tool description adds no additional parameter semantics beyond what the schema provides. The baseline is 3 given high coverage, and since the description does not elaborate on any parameter, it does not exceed that baseline.

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, and HTTP status') and a specific resource (a URL). This is clear, but it does not differentiate the tool from siblings like fetch-status or normalize-url, which could perform overlapping functions. The purpose is unambiguous, yet the lack of any comparison to alternative tools lowers the score from 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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or scenarios where this tool is preferred. It simply states what it does, leaving the agent to infer usage without support.

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