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

With no annotations, the description carries the full disclosure burden; it reveals only that the body is discarded. It does not state that other parameters are ignored, how redirects or errors are handled, or what a 'hint' means, and the schema's many 'discarded' fields are left unexplained.

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 text is very short and front-loaded, but it is under-specified for a tool with 9 optional parameters and no annotations. The brevity is not inherently bad, but it omits essential usage and parameter context, so the size is not appropriate to the tool's complexity.

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 no output schema, no annotations, and a complex optional schema, a two-sentence description is not enough. An agent cannot determine which parameter to populate, what output to expect beyond a status code, or how this relates to the many lookup and fetch siblings.

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 coverage is 100%, so the schema already documents each parameter at a basic level. The description adds that the relevant URL should be a public library docs URL, but it does nothing to clarify the role of city, feed, json, path, query, host, or ref in a tool whose description mentions only HTTP status.

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 output (HTTP status) and a specific resource class (public library docs URL), and notes the body is discarded. It is clear enough as a headline, but it does not reconcile the 9 unrelated optional parameters in the schema, so the actual scope remains ambiguous.

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 given about when to choose this over siblings like fetch-status, browser-url-ok, or normalize-url. The only implied use is for public library docs URLs, with no exclusions or alternatives.

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