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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It adds one useful note ('Page content is not stored'), but it does not disclose whether the tool makes network requests, requires permissions, handles errors, or any side effects. This is insufficient for a tool that likely interacts with external URLs.

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 redundancy. The main purpose is front-loaded, and the behavioral note is efficient. 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?

With nine parameters, no output schema, no annotations, and many sibling tools, the description is grossly incomplete. It does not explain the return format, error behavior, how the non-URL parameters are handled, or when to prefer this over fetch-status or normalize-url. The description covers only the primary function and leaves critical context unaddressed.

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 schema already documents each parameter individually, but the description does not clarify how the many unrelated-looking parameters (city, zone, json, etc.) relate to the stated purpose of returning URL metadata. This mismatch leaves the agent uncertain about whether those parameters are used or 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 states a specific verb and resource: 'Return host, scheme, and HTTP status for a URL.' However, it does not distinguish this tool from sibling tools like fetch-status or normalize-url, and the input schema contains nine parameters (ref, city, feed, json, path, zone, query) that are not mentioned in the description, creating confusion about the tool's actual scope.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions or exclusions, nor does it reference sibling tools. The only additional note ('Page content is not stored') is a behavior disclosure, not usage guidance.

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