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 side effects, read-only nature, what inputs are used for, or how results are presented. The parameter descriptions hint at some 'shape checks' and discarding, but the tool description itself is silent on 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 fluff or redundancy. It is concise and front-loaded with the core topic. However, its brevity borders on under-specification, which prevents a higher 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 9 optional parameters, no output schema, and no annotations, the description is extremely incomplete. It does not explain what the tool returns, how to call it, what inputs are expected to mean, or any behavioral context. An agent cannot use this tool correctly based on the provided information.

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 each parameter is individually documented in the schema. The tool description adds no meaning to parameters and does not explain their relevance to the catalog. The baseline of 3 applies because the schema already handles parameter semantics, though the description fails to tie them to the tool's 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 is a noun phrase stating the resource ('catalog of common HTTP status codes') but lacks a verb or action. It does not clarify how the tool operates or what it returns, and it does not distinguish itself from siblings like fetch-status or browser-url-ok, which also deal with HTTP status. The purpose is vague and under-specified.

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 is no mention of conditions, exclusions, or related tools. An agent has no way to decide if this is the right tool for a given task.

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