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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the body is discarded, but says nothing about network side effects, rate limits, error handling, or behavior for the other 8 parameters. The single-sentence description is insufficient for a tool with such broad parameter coverage.

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, two short sentences with no fluff. Information is front-loaded: the main action and the key behavioral detail (body discarded) appear first. It is not overly verbose, though the brevity contributes to incompleteness.

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 has 9 parameters, no annotations, and no output schema, yet the description only addresses a single URL-check scenario. It fails to explain what the tool does for the other parameters (city, feed, json, etc.) and provides no context on expected return values. This is inadequate for a tool of this complexity.

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?

Schema description coverage is 100%, and each parameter already has a clear description (e.g., 'Git ref name; discarded after the shape check'). The tool description adds no additional parameter-level meaning, but the high schema coverage justifies the baseline score of 3.

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 states a specific action: returning HTTP status for a public library docs URL and discarding the body. This is a clear verb-resource pair. However, it does not differentiate from sibling tools like fetch-status or browser-url-ok, and the schema contains 8 other parameters (city, feed, json, etc.) that the description ignores, creating ambiguity about the tool's actual scope.

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 on when to use this tool versus its many siblings. The phrase 'Body discarded' hints at a lightweight check, but there is no explicit mention of alternatives, prerequisites, or contexts where this tool is preferred. The agent is left to infer usage.

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