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. The single phrase 'short catalog' implies a read-only reference, but it does not describe side effects, network access, what happens to the inputs, whether any of them are discarded, or what the return value looks like. Some parameter descriptions mention discarded values, but that is in the schema, not the tool description, and an agent reading only the description would remain completely in the dark.

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 concise (6 words), but that is under-specification, not efficient conciseness. It lacks any structure or front-loaded details that would help an agent understand the tool's purpose or usage. Every word is present, but none of them are informative enough to guide correct invocation.

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 8 parameters, no output schema, no annotations, and unclear relationship to its siblings, the description is grossly incomplete. It does not explain how the catalog is queried, what the output format is, or why parameters like 'city' and 'feed' appear in an HTTP status code catalog. An agent cannot reliably select or call this tool based on the given definition.

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 contains descriptions for all 8 parameters (ref, url, city, feed, host, json, path), so schema coverage is high. The description itself adds no parameter information, but per the baseline rule, a 3 is appropriate when the schema already documents the parameters.

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 with no verb—it does not state what action the tool performs (e.g., returns, lists, looks up). It names a resource (HTTP status codes) and a kind (catalog), but this is largely a restatement of the tool name. The presence of 8 unrelated input parameters (ref, url, city, feed, host, json, path) further muddies what the tool actually does, and it 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 any of the siblings. There is no mention of conditions, alternatives, or exclusions. An agent would have no basis to choose this tool over fetch-status, web-fetch, or normalize-url, which all deal with URLs/HTTP in some form.

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