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

No annotations are present, so the description carries the full burden of behavioral disclosure. It says only 'short catalog' and gives no indication of what happens to the seven input parameters (some are discarded, some are cited), what processing occurs, or what output is produced. The behavior is entirely opaque.

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 superficially concise ('Short catalog of common HTTP status codes') but is under-specified to the point of being unhelpful. This is not tight, meaningful conciseness but rather a lack of substance. The single sentence does not earn its place because it conveys almost no operational information.

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?

For a tool with seven parameters, no annotations, and no output schema, this one-sentence description is drastically incomplete. It does not explain which parameter(s) to provide, how the 'catalog' relates to the inputs, what the tool returns, or how it differs from sibling tools. An agent would have no way to correctly invoke this tool.

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 provides detailed descriptions for all seven parameters (e.g., 'Git ref name; discarded after the shape check'), giving high schema coverage. The tool description itself adds no parameter information, but since schema coverage is high, the baseline of 3 applies. The description does not compensate for any gaps, but also doesn't need to.

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') with no verb indicating what the tool does when invoked. It names a resource (HTTP status codes) but fails to state the action (e.g., look up, validate, return) or how it relates to the many input parameters. This is more vague than a tautology but still leaves the tool's purpose ambiguous.

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 zero guidance on when to use this tool versus siblings like fetch-status, web-fetch, or the various *-shape tools. No conditions, exclusions, or alternative routing hints are provided. An agent cannot determine if this tool is for looking up status codes, validating inputs, or something else.

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