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

There are no annotations, so the description carries the full burden. It does disclose a key behavioral trait: 'Body discarded,' meaning the returned value is only an HTTP status. However, it does not mention whether the operation is read-only, how the extra schema parameters are treated, or any side effects.

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 two short sentences with no waste. The main purpose is front-loaded, and the behavioral trait 'Body discarded' is stated separately. It is concise, though the brevity comes at the cost of necessary context.

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 seven parameters, no annotations, and no output schema, the description is incomplete. It does not explain what a 'public library docs URL' is, how the various parameters interact, or when to prefer this over sibling status/shape tools. The mismatch between the single-purpose description and the heterogeneous schema is a significant gap.

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 input schema gives a description for every parameter, so schema_description_coverage is high. The tool description adds no parameter-level meaning and does not clarify how parameters like `city` or `json` relate to the stated purpose. Baseline 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 purpose: returning HTTP status for a public library docs URL and discarding the body. However, the input schema lists seven heterogeneous parameters (ref, city, feed, json, path) that are unrelated to this stated purpose, creating ambiguity about what the tool actually accepts. It also does not differentiate from sibling tools like fetch-status or web-fetch.

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?

The description provides no guidance on when to use this tool versus alternatives. It neither names sibling tools nor gives exclusions. The intended usage is only implied: use it when you need HTTP status for a public library docs URL.

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