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 states nothing about side effects, information retention, validation, or what the catalog does with the supplied parameters. The only behavioral hints are buried in the schema parameter descriptions, not the tool description.

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 short and lacks filler words, with the core noun phrase front-loaded. It is efficiently sized but at the expense of much needed substance.

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?

Given 9 optional parameters, no output schema, no annotations, and a highly ambiguous description, this tool is severely under-described. An agent has no way to know what to pass in, what output to expect, or which sibling tool to choose.

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?

Schema coverage is 100% and every parameter already has an individual description, so the baseline is 3. The main description adds no meaning about how the nine parameters relate to the tool's purpose.

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' identifies only the resource and is nearly a restatement of the tool name. It lacks a specific verb or behavior, and does nothing to distinguish this tool from siblings 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 about when to use this tool versus alternatives. With several similar sibling tools and nine optional parameters covering URLs, JSON, hosts, queries, and more, the description provides no selection criteria.

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