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

With no annotations, the description carries the full burden for behavioral disclosure, and it provides almost none. It doesn't state that the tool is read-only, deterministic, or what it returns, and it never explains that many input parameters are simply discarded; calling it a 'catalog' doesn't tell the agent what side effects or assumptions exist.

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 only eight words, but this is under-specification rather than efficient concision. It front-loads a noun phrase that adds little beyond the tool name, so the brevity does not meaningfully help an agent decide to use it.

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?

There is no output schema, no return-value description, and no explanation of how the eight parameters relate to the catalog. An agent cannot tell what output to expect, whether parameters select anything, or whether this tool even performs an operation, leaving the definition materially incomplete.

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 documents all eight parameters, so the baseline is 3 even though the description adds no parameter-level meaning. The description also fails to reconcile the schema's odd mix of 'discarded after' parameters with the stated catalog purpose, but the schema itself already provides those discarding details.

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,' which mostly restates the tool name rather than expressing a specific action. It doesn't say whether the tool returns a list, looks up one status, or operates on a given code, and it fails to distinguish the tool from siblings like fetch-status or normalize-url.

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 given about when to use status-catalog versus alternatives such as fetch-status, web-fetch, or validate-json. The phrase 'short catalog of common HTTP status codes' weakly implies a reference lookup, but there are no explicit conditions, exclusions, or alternative recommendations.

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