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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention any side effects, return format, or what happens with the parameters. It doesn't even acknowledge that parameters are discarded (as the schema suggests). 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 extremely short (one sentence), which is technically concise, but it lacks structure and substance. It is under-specified rather than efficiently compact. The single sentence does not front-load any useful operational detail.

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, the description is completely inadequate. It does not explain how to call the tool, what it returns, or why the parameters exist. An agent cannot infer correct usage from this description.

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 tool description adds no meaning beyond the schema, and in fact the schema's per-parameter descriptions are more informative than the tool description. The description fails to explain how these parameters relate to HTTP status codes, but per the rule, high coverage grants a baseline 3.

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, not a verb+resource. It says 'Short catalog of common HTTP status codes' but does not state what action the tool performs or how it relates to the nine unrelated parameters (ref, url, city, etc.). It does not distinguish itself from siblings like fetch-status or domain-shape. The purpose is ambiguous and does not clarify the operation.

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 on when to use this tool versus alternatives. No mention of context, exclusions, or when not to use it. The single sentence provides no decision support for an agent.

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