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

With no annotations, the description carries the burden for behavioral disclosure, and it does add one meaningful promise: 'Page content is not stored.' However, it does not state whether a network request is made, whether redirects are followed, or what happens on HTTP errors, so the behavioral picture remains partial.

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 operative outcome front-loaded and the privacy guarantee stated immediately after. Every word earns its place.

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 tool whose schema exposes seven distinct string inputs—ref, url, city, feed, host, json, and path—covering only URL behavior is incomplete. Without an output schema, the description also omits return-structure guidance for the host/scheme/HTTP-status result.

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 high and every parameter already has its own explanatory description, so the baseline applies. The top-level description adds primary-URL framing, but it does not clarify ambiguous fields such as path, whose schema description duplicates host, or explain how the non-URL fields fit together.

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 and result: return host, scheme, and HTTP status for a URL. It is not a tautology, though it does not explicitly distinguish this tool from siblings like fetch-status or normalize-url, nor does it acknowledge the other input fields in the schema.

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 explicit guidance about when to use this tool versus related siblings such as fetch-status, normalize-url, or web-fetch. The phrasing implies URL metadata use, but with many overlapping sibling tools, the absence of exclusions or alternative routing leaves the agent without sufficient direction.

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