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

The only behavior disclosed is 'Body discarded,' which implies the response excludes the body. However, it does not mention network side effects, error handling, rate limits, or the fact that many schema parameters are described as discarded or unrelated to the stated purpose.

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 only two short sentences, with no filler or redundant content. It is concise and easy to read, though the brevity sacrifices essential detail.

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 9 optional parameters, no output schema, and no annotations, the description is severely incomplete. It does not state the return format (e.g., status code only vs. headers), which parameter is primary, or how to handle the confusing array of seemingly unrelated inputs.

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 tool description adds no meaning about the parameters themselves. The schema descriptions are present but contradictory to the stated purpose (e.g., city for weather hints, zone for timezone, query for search length), and the description does not explain which parameter is the actual URL input or why the others are accepted.

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 names a verb and resource ('HTTP status for a public library docs URL') but 'public library docs URL' is ambiguous and it does not specify which of the 9 input parameters is actually used. It also fails to distinguish itself from sibling tools like fetch-status or browser-url-ok.

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 alternatives. No conditions, prerequisites, or contrasting examples are provided, leaving the agent to guess its intended role among many similar sibling tools.

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