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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only describes a static catalog and gives no indication of side effects, network access, authentication needs, rate limits, or return behavior. This is insufficient for a tool with a mutable-looking input schema.

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 very short and contains no wasted words, but it is under-specified rather than appropriately concise. It reads as a label rather than a functional description, which fails the purpose of a tool definition.

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 no output schema, no annotations, nine optional parameters, and many siblings, the description leaves almost everything to inference. It does not explain what inputs are for, what the tool returns, or how the parameters relate to the catalog, making it inadequate for an agent to select and invoke correctly.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter-level meaning, but the schema itself documents each parameter. However, the parameter meanings (e.g., Git ref, city weather, JSON validation, timezone) do not obviously connect to the stated purpose of an HTTP status code catalog.

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 is a noun phrase, 'Short catalog of common HTTP status codes,' that essentially restates the tool name without specifying an action. It adds the domain 'HTTP status codes' but does not say whether the tool looks up, lists, or checks status codes, and it does not distinguish it from siblings 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?

There is no guidance on when to use this tool versus alternatives. With many sibling tools such as fetch-status, browser-url-ok, and normalize-url, an agent is left guessing whether to call this for a lookup, a fetch, or something else.

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