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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention what the tool does with the parameters, what it returns, whether it performs network requests, or any side effects. The description is silent on all behavioral aspects.

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 short, but this is under-specification rather than conciseness. It lacks essential information about what the tool does, how to invoke it, or what output to expect. A concise description should be informative, not merely brief.

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 4 parameters, no required fields, no output schema, and a vague one-line description, the tool is not usable by an agent. There is no explanation of the tool's function, parameter usage, or return value. This is completely inadequate for a tool with this complexity and sibling context.

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 has 100% coverage with each parameter described, but the tool description adds no meaning linking these parameters (url, host, json, zone) to a 'status catalog'. The schema descriptions themselves seem inconsistent with the tool's purpose—e.g., 'url' is described as 'HTTPS URL to normalize or cite', which suggests a different functionality. The description fails to clarify how these parameters are used.

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 is a noun phrase 'Short catalog of common HTTP status codes' without a verb indicating what action the tool performs. It does not distinguish itself from siblings like http-504 or normalize-url, and the name 'status-catalog' is only slightly expanded. The purpose remains ambiguous—does it list codes, check a URL's status, or validate something?

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. There are no conditions, exclusions, or references to sibling tools. With siblings like http-504 and validate-json, an agent has no way to know which tool to select.

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