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

No annotations are provided, so the description must carry the full behavioral burden. It says nothing about side effects, input handling, or output format. The schema hints that inputs are 'discarded after the shape check' but the description does not clarify this behavior. This is a severe gap for a tool that likely performs validation.

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 one sentence, which is concise, but it is under-specified for a tool with 9 parameters and no annotations. It lacks essential operational details, so brevity here is not appropriate; it sacrifices completeness.

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 complexity (9 parameters, no output schema, no annotations), the description is grossly incomplete. It does not explain what the tool returns, how parameters are used, or when to invoke it. An agent has no way to call 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. However, the description adds zero meaning to the parameters, and the schema's own descriptions (e.g., 'discarded after the shape check') are cryptic and disconnected from the stated catalog purpose. The tool description fails to explain how parameters map to the catalog, lowering the score.

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 (catalog of HTTP status codes) but provides no verb or action. It is unclear how the 9 diverse parameters relate to the catalog, and there is no distinction from sibling tools like fetch-status or browser-url-ok. The purpose is only vaguely implied as a reference.

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 on when to use this tool versus the many siblings. There are no conditions, prerequisites, or alternative names mentioned. An agent cannot determine if this is the right tool for a task.

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