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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the word 'catalog', which only weakly implies a read-only reference. It never states that inputs are checked and discarded, that no disk access occurs, or what the output looks like. Those behaviors surface only in the schema's parameter notes, 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 single sentence is terse and front-loaded, but it is under-specified rather than concise for a tool with eight heterogeneous parameters. Every word earns its place only in the sense that there are few words; the omission of behavior, output, and usage makes the brevity a liability.

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 heterogeneous parameters, no annotations, and no output schema, a one-sentence description that fails to state the return value, input-selection rules, or sibling relationships is far from complete. The schema's per-parameter notes (e.g., 'discarded after the shape check', 'no disk access', 'titles discarded') provide fragmented context but do not assemble into a coherent behavioral picture.

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?

Although the schema documents all eight parameters (high coverage, so the baseline is 3), the description adds no parameter meaning and actively conflicts with the parameter set: a catalog of HTTP status codes has no evident use for a city name, RSS feed, JSON text, or file path. The description leaves the agent unable to tell whether it should pass one parameter, several, or none.

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 is nearly a tautology of the tool name ('status' + 'catalog'), adding only the domain 'common HTTP status codes' without any verb stating what the tool does. It never reconciles the stated purpose with its eight heterogeneous inputs (git ref, URL, city, feed, host, JSON, path), which imply checking/validation behavior rather than a static catalog. It also fails to differentiate the tool from siblings like fetch-status, web-fetch, or domain-shape.

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 zero guidance on when to use this tool versus any of its 13 siblings, several of which overlap heavily (fetch-status, web-fetch, validate-json, normalize-url). The description names no alternatives, no prerequisites, and no exclusions. An agent cannot determine whether to invoke this tool for a URL check, a JSON validation, or a static lookup.

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