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

The description does not disclose any tool behavior such as side effects, network calls, read-only guarantees, or whether inputs are ignored. The parameter descriptions imply values are discarded or used only for shape checks, but the tool-level behavior is completely opaque.

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 very short and does not waste words, but it omits essential context and the word 'short' adds no value. It is structurally minimal to the point of being underinformative.

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 9 parameters and no output schema, the description is far from complete. It lacks return format, example usage, parameter selection rationale, and any explanation of how a 'catalog of status codes' relates to the arbitrary input fields.

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?

Although all parameters have descriptions, they are a mismatched set (ref, city, json, zone, etc.) unrelated to HTTP status codes and do not explain how any of them should be used. The 'discarded after the shape check' notes add some semantics but create confusion rather than clarity.

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' is vague and does not state an explicit action or clarify whether it returns a static list, checks a URL's status, or maps inputs to codes. It reads more like a noun phrase than a tool description and does not connect to the provided parameters.

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 on when to use this tool versus sibling tools like fetch-status or browser-url-ok. No use cases, limitations, or selection criteria are provided.

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