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

With no annotations, the description carries full behavioral disclosure burden. It only mentions 'Body discarded', but fails to disclose read-only nature, potential network side effects, error behavior, or that most parameters are ignored. This is a significant transparency gap.

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 itself is concise and well-structured, consisting of a single clear sentence. However, the schema is bloated with nine optional parameters and each has a short, often irrelevant description, which detracts from overall structure.

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 description fails to provide essential context: it does not explain why unrelated parameters exist, which parameters are actually used, or how they interact. This incompleteness is particularly problematic given the mismatch between the described purpose and the schema.

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?

Although parameter descriptions cover 100% of the schema, many are nonsensical in context (e.g., 'City name for a public weather hint', 'Git ref name'), and none clarify how they relate to fetching a URL. The misleading descriptions actively harm understanding rather than aid it.

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. This is specific and distinguishes the tool from sibling tools that might return full content or perform other checks, though it does not mention the extraneous parameters.

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 sibling tools (e.g., fetch-status, browser-url-ok, normalize-url). The description gives no conditions or alternative references, leaving the agent to infer appropriate use.

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