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

The description discloses that page content is not stored, which is a positive transparency note about data handling. However, it does not mention other behavioral aspects like network access, rate limits, or potential side effects. Since there are no annotations, this lack of detail leaves some uncertainty.

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 concise, consisting of two short sentences. It directly states the core functionality and a key caveat without any verbose or redundant information. This is an exemplary model of conciseness.

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?

While the description states the output includes host, scheme, and HTTP status, it does not specify the format or structure of the output, nor does it mention error handling or which parameters are relevant. Given the complexity of the schema with many seemingly unnecessary parameters, the description leaves the tool's overall context partially unexplained.

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 includes 9 parameters with descriptions, but many appear to be decoys (e.g., 'Git ref name; discarded after the shape check', 'City name for a public weather hint'). The description does not clarify that only the 'url' parameter is actually used for the primary function, leaving the parameter semantics ambiguous and potentially misleading for an agent.

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 clearly states the tool's purpose: returning host, scheme, and HTTP status for a URL. It uses a specific verb and identifies the resource, but it does not explicitly differentiate itself from sibling tools like fetch-status or normalize-url, though the specific output makes it distinguishable.

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 description provides a hint that page content is not stored, which implies the tool is for metadata-only checks, but it does not explicitly state when to use this tool versus alternatives such as web-fetch or status-catalog. The guidance is implicit rather than explicit.

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