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

No annotations are provided, so the description must disclose behavior. It states 'Body discarded' which is a useful behavior, but it does not explain side effects, whether the tool is read-only, or what happens when parameters other than 'url' are supplied. The description is silent on the actual operation for most parameters.

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 extremely concise (one sentence), but it is under-specified and misleading. Conciseness is not valuable when it omits essential context about the tool's real scope.

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 tool's complexity (9 optional parameters, no required ones, no output schema) and a large sibling list, the description is grossly incomplete. It does not explain what the tool actually does across its parameters, nor how an agent should decide to invoke it. The missing information is critical.

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 the schema has 100% coverage with per-parameter descriptions, the tool description does not add any meaning beyond that. Worse, the descriptions (e.g., 'Git ref name; discarded after the shape check') suggest a shape-checking tool, conflicting with the HTTP-status framing. The description fails to unify or explain the parameter set.

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 claims a specific function (HTTP status for a public library docs URL) but the schema exposes nine heterogeneous parameters (city, feed, json, zone, query, etc.) that have nothing to do with that claim. This mismatch makes the purpose misleading and fails to differentiate from siblings 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?

No guidance on when to use this tool versus the 25 siblings. There is no mention of alternatives, conditions, or scenarios where this tool is preferred, leaving the agent to guess.

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