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. 'Short catalog' implies a read-only result, but it does not mention side effects, output format, pagination, or that input parameters appear to be discarded. The schema's 'discarded' qualifiers are not reconciled with the catalog behavior.

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 with no filler words and is easy to scan. However, the brevity comes at the cost of missing operational context, so it earns a high, but not top, score.

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?

For a tool with seven parameters and no output schema or annotations, a one-phrase description is materially incomplete. An agent cannot determine the return format, whether any parameter is required, what 'common' means, or how the conflicting 'discarded' parameter descriptions relate to the catalog.

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 description does not explain any of the seven parameters or how they relate to the HTTP status catalog. Although each parameter has a schema description, those descriptions seem unrelated to a catalog (e.g., 'City name for a public weather hint; discarded after the call') and do not clarify whether or why the parameters affect the output.

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 specific resource ('common HTTP status codes') and indicates a catalog, so an agent can generally infer what the tool is about. However, it lacks an explicit verb, uses a noun phrase rather than an actionable statement, and does not differentiate itself from siblings like fetch-status or browser-url-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, when not to use it, or how it compares to sibling tools. The description says nothing about input requirements, optionality, or contexts where a more specific tool would be better suited.

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