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

No annotations are provided, so the description carries the full burden of explaining behavior. It does not disclose side effects, output shape, whether inputs are read-only, or what happens when multiple parameters are supplied.

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 concise in length, but it sacrifices necessary detail and structure. It does not front-load the actual operation or parameter usage.

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 nine optional parameters and no output schema, the tool needs substantial contextual explanation. The description is far too incomplete to tell an agent what input to supply, what output to expect, or how to handle the conflicting parameter hints.

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 descriptions give individual parameter hints, but the tool description does not explain how parameters like url, json, path, zone, or query relate to a catalog of HTTP status codes. This creates a semantic mismatch and leaves the agent unsure which parameter is relevant.

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 the resource as a 'catalog of common HTTP status codes', but does not state what action the tool performs or how this relates to the tool's name. It is neither a tautology nor fully misleading, but it is too vague to distinguish effectively from sibling tools like fetch-status or wiki-title-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 such as fetch-status, normalize-url, or validate-json. The description provides no context, prerequisites, or examples of appropriate invocation.

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