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

The description transparently states that the body is discarded and the target must be a public URL. It doesn't disclose redirect handling, error cases, timeout behavior, or output format, and several schema parameters are described only as discarded without explaining why they are accepted.

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 prose description is concise and front-loaded, but the overall tool definition is structurally bloated by seven irrelevant optional parameters. The single sentence earns its place, yet the parameter list adds noise rather than clarity.

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 is too sparse to be complete in context: it doesn't specify what the agent should pass, how to interpret the response, or when to prefer this tool over the many sibling URL/fetch/status tools. The lack of an output schema and required parameters leaves critical usage details implicit.

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?

The schema is highly misleading: 9 optional parameters are listed but only 'url' is relevant to the described fetch behavior, and even that description says 'normalize or cite' rather than fetch. Other parameters like 'city', 'zone', and 'json' are unrelated to HTTP status checks, and no parameter is marked required despite the tool needing a URL.

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?

Description clearly states the tool returns HTTP status and content type for a public URL and discards the body, giving a specific action and resource. However it is a noun phrase rather than an explicit verb and doesn't distinguish itself from related sibling tools like fetch-status.

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?

No guidance is provided about when to use this tool instead of related siblings such as browse-url-ok, fetch-status, or normalize-url. The only behavioral hint is 'Body discarded', which implies lightweight use but is not an explicit selection criterion.

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