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

With no annotations, the description carries the burden for behavioral disclosure. It adds one meaningful trait—'Page content is not stored'—and states the returned fields, but it does not mention side effects, validation failures, rate limits, or whether all inputs are ignored except url.

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 primary behavior front-loaded and the privacy guarantee as a useful second sentence. It reads efficiently, though the terse style underserves a seven-parameter tool.

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 no annotations, no output schema, and seven schema parameters, yet the description does not explain how to select among url, host, path, feed, or which inputs matter. This is insufficient for an agent to reliably invoke 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 input schema already provides descriptions for all parameters, so this is a high-coverage case where the baseline is 3. The main description adds no parameter-level meaning, and the presence of many seemingly discarded or alternate inputs like ref, city, feed, json, and path remains unexplained.

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 specifies a concrete outcome (host, scheme, HTTP status) for a URL, so an agent can infer the tool is a citation/status check rather than a fetch or normalize operation. It does not explicitly differentiate it from sibling tools like fetch-status or normalize-url, so it lacks full sibling distinction.

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 on when to use this tool versus fetch-status, normalize-url, web-fetch, or other siblings. There are no prerequisites, exclusions, or alternative routing hints.

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