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

With no annotations, the description carries the transparency burden, but it only discloses non-storage of page content. It does not state whether the URL is fetched over the network, whether redirects are followed, or what happens on errors or timeouts.

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 a single focused sentence that states the output and a key limitation. There is no unnecessary detail or verbosity.

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 description lacks output format and error semantics, and it does not reconcile the focused URL operation with the broad, heterogeneous input schema. An agent cannot confidently infer full tool behavior from the provided text.

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?

Although every parameter has a schema description, the tool description leaves the relationship between the focused URL behavior and the eight other optional parameters unexplained. It is unclear whether ref, city, feed, json, path, zone, and query are accepted, ignored, or affect the result.

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 that the tool returns host, scheme, and HTTP status for a URL, and it explicitly says page content is not stored. This makes the core action clear and distinguishes it from content-fetching tools, though it does not explain the 'citation' name.

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 on when to use this tool versus siblings like fetch-status, browser-url-ok, normalize-url, or web-fetch. The statement that page content is not stored is more of a privacy note than a concrete usage rule.

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