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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only labels the tool as a 'short catalog' without revealing return format, side effects, or how inputs are treated. The schema hints that many parameters are discarded, but the description offers no clarification.

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 concise sentence with no waste, but it is under-specified for a tool with a complex eight-parameter schema. It provides minimal information without addressing the schema's breadth, so it is not optimally structured.

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 the complexity of the input schema and the absence of an output schema or annotations, this description is far from complete. An agent cannot determine how to invoke the tool, what arguments to pass, or what result to expect beyond a vague notion of catalog content.

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 the input schema documents each parameter, the description does not connect them to the catalog of HTTP status codes. The parameters (ref, url, city, feed, json, etc.) appear unrelated to the stated purpose, leaving agents unable to determine the correct input to provide.

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" essentially restates the tool name 'status-catalog' without a clear verb or action. It does not say how the tool operates or what it returns, and it fails to distinguish it from siblings like fetch-status or normalize-url.

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 given for when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or sibling tool comparisons, leaving an agent without direction for selection.

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