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

With no annotations, the description must carry the full behavioral burden. It does not disclose whether the tool returns a single code, a list, a mapping, or performs network lookups; the parameter notes like 'discarded after the shape check' hint at side-effect-free behavior but are not organized into a coherent behavioral model.

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?

One short sentence, but brevity is not conciseness; the sentence omits the essential action and is misleading relative to the schema. It does not front-load a clear verb or resource.

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?

A tool with 8 heterogeneous parameters, no output schema, and no annotations needs a much richer description to be callable. The current definition gives no indication of expected output, how inputs are used, or which inputs are required, so an agent cannot reliably select or invoke it.

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 describes all 8 parameters individually (e.g., 'City name for a public weather hint; discarded after the call'), but these descriptions are disconnected from the tool description; they suggest the tool acts as a generic shape-checker or normalizer rather than a status-code catalog. Schema coverage is high, but the tool description does not help reconcile the mismatch, so the value is limited.

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 a noun phrase, not a verb phrase; it never states what the tool actually does (retrieve a code, validate a response, map inputs to codes?). The input schema clashes with the description: parameters like city, feed, and json have no obvious relation to HTTP status codes, so an agent cannot infer the tool's purpose.

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 when-to-use guidance, no alternatives mentioned, and no context on when status-catalog should be chosen over sibling tools like fetch-status or web-fetch. The description implies it is a static reference, but nothing clarifies its role in a workflow.

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