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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does provide one meaningful behavior: page content is not stored. However, it does not mention authentication needs, rate limits, error behavior, whether a network request is actually made, or whether inputs are logged, leaving notable transparency gaps.

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 the primary behavior front-loaded. The second sentence about page content not being stored is a meaningful behavioral caveat rather than filler. It is highly concise and well structured.

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 tool exposes nine optional parameters, has no annotations, and has no output schema, yet the description only addresses the URL case and never explains the role of the other parameters. An agent cannot reliably determine which parameter is primary, whether parameters are mutually exclusive, or what the result shape looks like.

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 only connects the output to a URL and adds nothing beyond the schema's parameter descriptions; it also leaves unclear how the many unrelated-looking optional parameters like city, feed, json, and query relate to the stated 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 clearly specifies the action (return), the resource (a URL), and the concrete outputs (host, scheme, and HTTP status), so an agent can understand the core function quickly. However, it does not distinguish this tool from siblings like fetch-status or normalize-url, and the 'citation' name is not explained.

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 guidance about when to use this tool instead of fetch-status, web-fetch, normalize-url, or other siblings. The note that page content is not stored hints at a safe read-only use case, but it stops short of an actual when-to-use or when-not-to-use statement.

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