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

Because no annotations are provided, the description carries the full disclosure burden. It does add an important behavioral fact ('Page content is not stored') and implies a network request via HTTP status, but it leaves side effects, redirect behavior, and the role of the many discarded parameters unexplained.

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 short sentences with the main result front-loaded and a meaningful privacy/behavior note in the second sentence. There is no wasted wording.

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 URL-metadata request, calling with only 'url' is supported and the returned values are named, so the description is minimally usable. However, with nine optional parameters, no output schema, and no annotations, it leaves the overall scope ambiguous—especially why city, feed, JSON, path, timezone, and query parameters exist.

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 the baseline is 3 and each parameter has an individual explanation. The description adds only the output context for the URL parameter and does not clarify the meaning or selection logic for the other eight optional parameters, but it does not contradict 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 concrete result (host, scheme, HTTP status) for a specific resource (a URL), so the core operation is clear. It does not explicitly distinguish itself from sibling URL tools like fetch-status or normalize-url, but the 'Page content is not stored' clause provides some differentiation.

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 prefer this tool over the many sibling URL/status tools, nor any when-not-to-use or alternative conditions. The only implicit cue is that it operates on a URL and does not store page content, which is not enough for routing decisions.

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