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

With no annotations provided, the description must carry the full burden of behavioral disclosure. The only behavioral hint is 'Body discarded,' which implies the tool returns status but not the body. However, it omits critical behavior like whether network access is involved, any side effects, rate limits, or how it handles the varied parameters. For a tool that likely performs HTTP requests, this is insufficient.

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 concise (two sentences) and front-loads the primary action. However, it is too sparse to convey the tool's actual scope, making it under-specified rather than appropriately sized. It doesn't waste words, but it lacks necessary content.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description is woefully incomplete. It fails to explain how the parameters relate to the stated purpose, what the return value looks like beyond 'HTTP status', or how the tool behaves with each parameter type. An agent would be unable to use this tool correctly without additional information.

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 schema descriptions cover 100% of parameters and each has a descriptive note (e.g., 'discarded after the shape check', 'no disk access'). The description adds no parameter information, but since the schema already documents them, a baseline score of 3 is appropriate.

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 function ('HTTP status for a public library docs URL') but it only covers one use case while the schema accepts 9 unrelated parameters (city, json, path, zone, query). This makes the actual scope misleading and fails to distinguish it from siblings like fetch-status or normalize-url, which also deal with URLs and status.

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 on when to use this tool versus alternatives such as fetch-status, browser-url-ok, or normalize-url. There is no mention of conditions, exclusions, or contexts that would help an agent choose this tool.

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