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

With no annotations provided, the description carries the behavioral burden. It does disclose a meaningful behavior: page content is not stored, which suggests a privacy-conscious, lightweight operation. However, it does not clarify whether the tool makes a network request, follows redirects, or has any side effects beyond the stated output, leaving gaps for an agent to reason about.

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 no filler. The primary action and output are front-loaded, and the additional privacy caveat is a valuable second sentence that 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?

Given 9 parameters, no output schema, no annotations, and many overlapping sibling tools, this description is too thin. It does not explain the purpose of the extra parameters, the expected return format, or error behavior, leaving an agent with significant ambiguity 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?

Schema description coverage is 100%, so the schema already documents all 9 parameters. The description reinforces that 'url' is the key input by tying the output to a URL, but it does not explain how the other optional parameters such as city, zone, or json relate to the citation behavior, nor does it clarify whether they should be ignored.

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 a specific verb ('Return'), resource ('a URL'), and output values ('host, scheme, and HTTP status'). This is more specific than the tool name alone and helps distinguish it from content-fetching siblings like web-fetch, though it does not explicitly differentiate from fetch-status or normalize-url.

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 gives no explicit when-to-use or when-not-to-use guidance, and it does not mention any alternatives. The phrase 'Page content is not stored' weakly implies this is not for content retrieval, but there is no clear directional signal about when to prefer this over fetch-status, normalize-url, or web-fetch.

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