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

The description provides one useful behavioral guarantee: 'Page content is not stored,' and the verb 'Return' implies a read-only operation. However, with no annotations, the description carries the full burden and still omits important details like whether a network request is made, which parameters are actually honored, and how unreachable URLs are handled.

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 two short sentences with no filler, and the main behavior is front-loaded. The privacy note is relevant and earns its place, though the extreme brevity contributes to the overall incompleteness.

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?

With no output schema, no annotations, and nine optional parameters spanning unrelated domains like ref, city, json, zone, and query, this description is not sufficient. It does not specify the response format, which parameters to provide for a normal citation request, or why so many unrelated parameters are accepted.

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 baseline is 3. The tool description adds minimal parameter meaning beyond restating that 'url' is relevant; it does not clarify the roles of the other eight parameters or how they relate to the citation behavior.

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 names a specific action and resource: 'Return host, scheme, and HTTP status for a URL.' This is clear enough to infer the core purpose. However, it does not differentiate from sibling tools like normalize-url or fetch-status, and it leaves the nine-parameter schema unexplained.

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 guidance about when to use this tool versus alternatives such as fetch-status, browser-url-ok, or normalize-url. No exclusions, prerequisites, or decision rules are provided, so the agent must guess the intended use case.

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