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

With no annotations, the description carries the full burden of behavioral disclosure. It says nothing about read-only vs. mutating, return format, side effects, or whether parameters are ignored or used materially. The word 'catalog' might imply a read-only lookup, but that is an inference, not a disclosure.

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 short sentence, but it also is severely under-specified for a tool with 9 parameters. It is not conciseness; it is an absence of information. There is no front-loading of critical information, because nothing beyond a vague noun phrase is provided.

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 tool has 9 parameters, no output schema, and no annotations, this description is wholly incomplete. It cannot tell the agent what to send, what to expect back, or why this tool exists alongside 30+ siblings. The description offers essentially no context, so an agent would be unable to use this tool correctly.

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 description coverage is 100%, so the baseline is 3. The description itself adds no additional meaning to the parameters; it does not explain how the 9 disparate parameters (city, host, json, zone, path) relate to a status code catalog. Still, because the schema fully describes each parameter, the description is not required to repeat those details. The mismatch between the stated purpose and the parameter list remains a gap, but the schema fills the immediate semantic need.

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 phrase 'Short catalog of common HTTP status codes' identifies the resource (HTTP status codes) and implies a noun-based catalog, but no verb or action is specified. It does not distinguish itself from siblings like 'fetch-status' or 'browser-url-ok', which could also involve status codes. The purpose remains ambiguous: is it a static reference list, or does it use the 9 parameters to filter/lookup?

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 zero guidance on when to use this tool versus the many sibling tools. No context is provided for what kind of task should route the agent here, and no exclusions point to a more appropriate tool. The description does not explain whether it is intended for spot-checking a URL status, listing all codes, or something else.

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