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 only labels the tool as a 'short catalog' and says nothing about side effects, return format, network behavior, or security implications, leaving the agent completely in the dark about what happens when the tool is invoked.

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, brief sentence and is concise without redundancy. However, it is under-specified rather than appropriately sized, and lacks any structure that would help an agent understand the tool's purpose or usage.

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 eight parameters, no annotations, and no output schema, a one-phrase description is completely inadequate. The description does not explain what the catalog contains, how to query it, what response to expect, or why such diverse inputs are accepted.

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?

All eight parameters have individual descriptions in the input schema, so schema coverage is high. The tool description adds no parameter-related meaning but does not need to because the schema already documents each parameter; however, it fails to explain why parameters like city, feed, and json relate to a status code catalog.

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' simply restates the tool name and provides no verb, action, or behavioral detail. It does not differentiate the tool from sibling tools like fetch-status or compatibility, leaving an agent unsure what operation it performs with the varied inputs.

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 gives no guidance on when to use this tool versus alternatives. There is no mention of conditions, exclusions, or preferred sibling tools despite a large set of related tools such as fetch-status, web-fetch, and compatibility.

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