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

It discloses that the body is discarded, and some parameters are explicitly noted as 'discarded after the shape check.' However, it does not mention any network side effects, authentication, or rate limits, leaving ambiguity about the actual behavior given the eclectic parameter list.

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 brief and to the point, consisting of two short sentences. It avoids unnecessary fluff, though the parameter list is extensive and not summarized.

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?

Given the many unrelated parameters and lack of an output schema, the description fails to explain how to interact with the tool or what to expect. It does not clarify which parameters are actually used or how they affect the result, leaving the agent without sufficient context.

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 every parameter has a description, they are largely irrelevant to the stated function (e.g., city, timezone, query). The descriptions appear to be generic placeholders, not tied to the tool's purpose, making them misleading rather than helpful.

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 tool's core function: returning HTTP status and content type for a public URL while discarding the body. This distinguishes it from more general fetch tools, though it doesn't mention the unexpected extra 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?

The description provides no guidance on when to use this tool over alternatives like fetch-status or browser-url-ok. No conditions, examples, or comparisons are given.

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