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

With no annotations, the description must carry transparency, but it only discloses that page content is not stored. It fails to mention network behavior, side effects, error conditions, or the fact that the many listed parameters appear to be ignored, which could mislead an agent.

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 and front-loaded, with two short sentences that state the core function and a key behavioral guarantee. It earns its place, though the massive irrelevant parameter list makes the overall definition feel bloated.

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 is incomplete for practical use: there is no output schema, no required parameter, no explanation of the output format for host/scheme/status, and no guidance on error handling. The presence of nine optional parameters with unrelated descriptions leaves an agent with little confidence about how to invoke the tool 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?

Although every parameter has a schema description, the descriptions are unrelated to the stated purpose: ref, city, feed, json, path, zone, and query have nothing to do with returning host, scheme, or HTTP status. The url parameter is the only plausible input, and with all parameters optional, there is no clear instruction on what to pass or why the others exist.

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 clear outcome—return host, scheme, and HTTP status for a URL—and adds that page content is not stored, but it does not differentiate this from sibling tools like fetch-status or normalize-url. The presence of nine unrelated optional parameters in the schema further muddies what the tool actually does.

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 given about when to choose this tool over alternatives such as fetch-status, browser-url-ok, or web-fetch. The statement about page content not being stored hints at a use case but does not explicitly explain when this tool is appropriate.

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