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, and it discloses nothing. It does not state whether the tool returns a list, performs lookups, validates inputs, or has side effects; the schema's 'discarded after the check' notes are the only behavioral hints, and they are not in the description.

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 brief, but brevity here is under-specification rather than efficient conciseness. It lacks the structural elements needed to orient an agent, such as a clear action, input-output relationship, or usage context.

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 heterogeneous parameters and no output schema, the description is grossly incomplete. It does not explain the purpose of the parameters, what the tool returns, or how it fits into the broader toolset, leaving the agent without enough information to invoke it 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?

The schema already provides descriptions for all seven parameters, so schema coverage is effectively 100%, which sets a baseline of 3. The description itself adds no parameter-level meaning, but it does not need to because the schema already documents each parameter.

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 'Short catalog of common HTTP status codes' is little more than a restatement of the tool name and lacks a verb or explicit action. It does not clarify how the many input parameters (ref, url, city, feed, json, path) relate to a status-code catalog, and it offers no basis for distinguishing this tool from siblings like fetch-status or web-fetch.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of suitable inputs, expected scenarios, or exclusions, leaving the agent to guess how 'status-catalog' relates to the sibling tools.

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