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

With no annotations provided, the description must carry the burden of behavioral disclosure. It mentions 'Body discarded' which is a useful detail, but it does not clarify whether a network request is made, what exactly is returned (status code, status text), or any rate limits or side effects. The schema notes that many parameters are 'discarded after' some check, but the tool description does not explain this behavior.

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 one short sentence, which is concise, but it is under-specified. It lacks critical context about the tool's behavior and parameter usage. The sentence is not front-loaded with the most important guidance; it merely states the purpose and discards the body.

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 has no annotations, no output schema, and 9 parameters, the description is severely incomplete. It does not explain the return format, which parameters are required or optional for a successful call, or any constraints. An agent cannot reliably decide how to invoke this tool based on the provided 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 covers all parameters with descriptions, so the baseline is 3, but the tool description does not add value beyond the schema. It does not clarify which of the 9 parameters are actually relevant to the stated purpose (HTTP status of a library docs URL). The description implies only 'url' matters, yet the schema includes many others, leaving the agent uncertain about how to use them.

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 verb and resource: it checks the HTTP status of a public library docs URL. However, the input schema includes many unrelated parameters (city, zone, query, json, path, etc.) that are not mentioned, creating confusion about the tool's actual scope. It also does not 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?

No guidance is given on when to use this tool instead of alternatives like fetch-status or normalize-url. The description does not mention any exclusions or conditions for selection, leaving the agent to guess based on the name and brief purpose.

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