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 does not state whether the tool is read-only, what side effects occur (e.g., discarding inputs), what the output format is, or how the parameters influence the result. The description is nearly empty of behavioral content, making it opaque to the agent.

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, which is concise but under-specified. It provides almost no actionable information, and the brevity is not a strength because it fails to communicate essential usage or behavior. The description is not structured to front-load critical details; it is simply too minimal to be useful.

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 grossly incomplete. An agent has no idea what the tool does, what it returns, or when to use it. The description offers virtually no context to support correct invocation or interpretation of results.

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 input schema has 100% coverage with descriptive parameter comments, so the baseline is 3. The description adds no extra meaning about how the parameters are used or related to status codes, but the schema already documents each parameter adequately. No value is added beyond the schema, so a 3 is appropriate.

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 states the tool is a 'catalog of common HTTP status codes,' which only restates the name and does not explain what the tool actually does with the nine provided parameters. It fails to distinguish this tool from siblings like fetch-status or web-fetch, and gives no indication that it evaluates inputs to produce a status code.

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. The description does not mention any conditions, contexts, or exclusions, and the sibling list includes many tools that could overlap (fetch-status, web-fetch, validate-json). An agent would have to infer usage from the parameter names alone.

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