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 does not state whether the tool is read-only, what it returns, whether it performs network requests, or how parameters are used. 'Catalog' implies a static reference, but that is only an inference.

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 one short sentence and is front-loaded, but it is an under-specified title rather than a genuine description. Given seven parameters and unclear usage, the brevity harms clarity rather than helping 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?

With no annotations, no output schema, seven parameters, and a likely sibling tool named fetch-status, a one-line description is far too incomplete. There is no mention of return values, invocation pattern, sibling differentiation, or even whether parameters are required.

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 provides descriptions for all seven parameters, so schema coverage is high and the baseline is 3. However, the tool description adds no connection between these parameters and the 'status catalog', and several parameters like 'city' and 'feed' seem unrelated to HTTP status codes.

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 names the resource ('catalog of common HTTP status codes') but uses no verb, so it is not clear whether the tool returns a static list, looks up a code, or validates something. It does not distinguish itself from the sibling fetch-status, which could easily be confused with a status-related operation.

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 such as fetch-status or browser-url-ok. The description gives no selection criteria, no exclusions, and no hint about what kind of request should be routed here.

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