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

With no annotations provided, the description carries the full behavioral burden, and it is nearly silent here. It never states whether the catalog is static or filtered, whether all input parameters are discarded (schema mentions 'discarded' only in parameter descriptions), what the output shape is, or whether there are side effects. The word 'catalog' hints at a read-only reference, but that is not explicit.

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 a single short sentence with no filler, and it places the subject ('HTTP status codes') immediately. It is under-specified, but that deficiency is better attributed to other dimensions; structurally, it is clean, front-loaded, and easy to parse.

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 9 optional parameters, no output schema, no annotations, and 30 siblings, the description must clarify the return format, the role of the parameters, and when to choose this tool. It leaves all of these unresolved. Which catalog entries are returned and whether any parameter can filter them is left entirely to inference.

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 schema covers all 9 parameters with descriptive text, so the baseline of 3 applies even though the tool description adds nothing about them. The description does not explain how a Git ref, city, timezone, or JSON text relates to the status-code catalog, so it fails to compensate for the obvious semantic mismatch.

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 identifies a specific resource — a catalog of common HTTP status codes — and distinguishes it from tools that fetch or test URL statuses. However, it offers no explicit differentiation from siblings such as fetch-status or browser-url-ok, and the 9 unrelated parameters make the actual behavior harder to pin down.

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 gives no guidance on when to choose this tool over the 30 siblings, nor exclusions or alternatives. An agent has no information on whether to use it for lookups, teaching, or mappings, and cannot distinguish it from status-checking tools in the sibling list.

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