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

There are no annotations, so the description carries full responsibility. The description only says it's a 'catalog', implying an informational read-only operation, but it doesn't disclose any side effects, return format, or limitations. It fails to explain what happens when called or how the many parameters affect behavior.

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 at nine words, but it's under-specified rather than efficiently informative. It lacks structure or front-loading of critical information beyond the basic purpose. A 3 reflects that it is brief but not appropriately detailed.

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, and no annotations, the description is severely inadequate. It doesn't explain what the tool does with the parameters, what it returns, or when it's appropriate to use. An agent cannot make an informed decision about calling this tool based on the current 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?

Schema coverage is 100%, so each parameter has a description. However, the tool description adds nothing about how parameters relate to the catalog purpose. The nine parameters (ref, url, city, feed, host, json, path, zone, query) seem arbitrary and disconnected from HTTP status codes, making it unclear why an agent would supply them. The description does not compensate for this 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 states a clear purpose: a short catalog of common HTTP status codes. It distinguishes itself from siblings like fetch-status (which fetches a URL's status) by being a reference catalog rather than a network operation. However, it doesn't specify what action an agent performs with this catalog—whether it retrieves codes, explains them, or something else.

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 provided on when to use this tool versus alternatives. It doesn't state conditions, prerequisites, or exclusions. An agent would have no basis for choosing this over fetch-status or other status-related tools.

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