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

With no annotations, the description carries the full burden, yet 'Short catalog of common HTTP status codes' discloses no side effects, network access, or return behavior. Only the schema parameter notes ('discarded after the shape check', 'no disk access', 'titles discarded') hint at non-usage of inputs, and those live outside the description itself.

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 nine-word noun phrase with no wasted words and is front-loaded with the topic, so it is concise. However, it is under-sized for a tool with nine parameters and offers almost no actionable structure for an agent deciding how to invoke it.

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 parameters that appear unrelated to the stated purpose and no output schema, the one-line description leaves the input/output contract almost entirely unexplained. An agent cannot predict what the tool does with a city name, a Git ref, or a timezone, nor what the catalog returns.

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 coverage is 100%, so the baseline is 3. The per-parameter notes do add some meaning beyond bare names (discard semantics, 'no disk access', 'titles discarded'), but several notes describe behaviors recycled from other tools (weather hint, timezone, URL normalization, JSON validation) and never connect the parameters to the catalog's stated purpose.

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 names a resource ('short catalog of common HTTP status codes') but uses no action verb and never says what the tool actually does with its inputs. The nine optional parameters (git ref, city, timezone, RSS feed, JSON text, file path) bear no visible relationship to an HTTP status-code catalog, leaving the tool's true function ambiguous.

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 call this tool versus siblings like fetch-status, normalize-url, weather-hint, or validate-json. There is no 'use when', 'use instead', or any comparative language anywhere in the description.

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