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

The description states that the body is discarded, which is useful. However, with no annotations, it does not disclose output format, error behavior, or explicitly confirm read-only behavior beyond the implied HTTP status check.

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?

Two short sentences, both necessary and free of redundancy. The description is tightly scoped and easy to parse.

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?

With 9 optional parameters, no output schema, and no annotations, the description is too sparse. It leaves unclear which inputs are actually needed, what the return value looks like, and what failure modes may occur.

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 descriptions cover all 9 parameters, so the baseline is 3. The top-level description only identifies URL and does not clarify why city, feed, query, and others are present; the url schema description ('normalize or cite') also conflicts with the stated HTTP-status purpose.

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?

Identifies the resource (public library docs URL) and result (HTTP status), but uses a noun phrase rather than an explicit verb, and 'public library docs' is ambiguous. With siblings like fetch-status and web-fetch, it needs more precision to distinguish the exact purpose.

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 about when to use this tool versus fetch-status, browser-url-ok, or web-fetch. It provides no use-case context or exclusion criteria.

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