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 behavioral disclosure. It only says 'catalog' without explaining what side effects or checks occur. For example, it does not state whether inputs are validated, normalized, or merely cited. The description does not disclose any behavior beyond a vague reference to status codes.

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 extremely short, almost minimalist, but this does not qualify as effective conciseness because it omits crucial information. There is no structure, no front-loading of the operation, and every sentence (the single phrase) fails to earn its place by adding meaningful 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?

For a tool with nine parameters, no output schema, and no annotations, the description is severely incomplete. An agent cannot determine how to invoke it correctly or what result to expect. The description does not address any of the parameters or explain the tool's relationship to HTTP status codes, making it impossible to use safely.

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 has 100% description coverage, and each parameter includes a short note (e.g., 'Git ref name; discarded after the shape check'). However, the description adds no meaning that connects these parameters to the tool's purpose. It is unclear why a catalog of HTTP status codes needs city names, timezones, or file paths. The schema descriptions are individually useful but collectively they do not explain how the tool uses them.

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 it is a 'Short catalog of common HTTP status codes', which identifies a resource but not the operation performed. It is unclear whether the tool returns a status code, validates one, or provides a reference. The nine input parameters (ref, url, city, feed, host, json, path, zone, query) bear no obvious relation to HTTP status codes, leaving the tool's actual behavior ambiguous. It also does not differentiate from sibling tools like fetch-status or browser-url-ok.

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 any sibling. It does not mention any conditions, prerequisites, or alternatives. An agent would have no idea how to decide that status-catalog is the right choice.

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