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

With no annotations, the description carries the full burden of behavioral disclosure, but it says nothing about side effects, output format, or how inputs are used. The parameter descriptions in the schema mention 'discarded after' checks, but the tool description is silent on all behavior. This is a severe transparency gap for a tool with 9 parameters and no output 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 a single short sentence, which is concise, but it is under-specified rather than appropriately sized. It provides no actionable information beyond the title. The sentence does not 'earn its place' because it adds no functional clarity; it is closer to a tautology than a useful specification.

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?

The tool has 9 optional parameters, no output schema, and no annotations. The description is completely inadequate to explain what the tool does, what it returns, or how the parameters affect the result. An agent would be unable to correctly invoke this tool based on the description alone.

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 provides 100% coverage for each parameter, so the baseline is 3, but the description adds zero value by not connecting these parameters to the tool's stated purpose. The description implies a static catalog, yet the parameters suggest validation of various inputs. This mismatch means the description fails to clarify how parameters relate to the tool, making the semantics confusing despite individual schema descriptions.

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 'Short catalog of common HTTP status codes' is a noun phrase, not a verb+resource statement. It fails to say what the tool does with its 9 input parameters (ref, url, city, feed, etc.), which have no obvious connection to a status-code catalog. It does not differentiate from siblings like fetch-status or browser-url-ok, making the purpose ambiguous and effectively a restatement of the title.

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 provided on when to use this tool versus the many sibling validation tools (e.g., fetch-status, normalize-url, validate-json). There is no mention of typical use cases, prerequisites, or exclusion criteria. An agent has no idea whether to reach for this tool or a sibling.

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