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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states that the body is discarded, but does not explain what happens with the other parameters (ref, city, feed, etc.) or any side effects, error handling, or security considerations. The behavior beyond the basic fetch is opaque.

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, concise sentence that front-loads the primary function and includes a key behavioral detail (body discarded). It has no wasted words, but its brevity may come at the cost of necessary context, making it slightly under-specified for a tool with many parameters.

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 and no output schema, the description is severely incomplete. It does not explain how the parameters are used, what the return value looks like, or how they align with the stated purpose of checking HTTP status. An agent would lack the information needed to correctly invoke this tool in a real scenario.

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 coverage is 100% and each parameter has a descriptive label, so the schema already provides substantial meaning. The tool description adds no additional context about how these parameters relate to the core fetch operation or which ones are primary, so it does not improve on the baseline set by the schema.

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 the core function: retrieving HTTP status and content type for a public URL, with the body discarded. However, it does not differentiate from siblings like fetch-status or browser-url-ok, and it omits any mention of the other eight parameters, which could confuse an agent about the tool's full 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?

There is no guidance on when to use this tool versus the many similar siblings (e.g., fetch-status, normalize-url, browser-url-ok). No conditions, exclusions, or alternative references are provided, leaving the agent to guess which tool fits a given scenario.

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