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. 'Short catalog' weakly implies a read-only reference resource, but it does not state whether the tool has side effects, whether it reads or returns data, how the inputs affect behavior, or what output format to expect.

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 short but not usefully concise; it is under-specification rather than tight communication. A 14-word noun phrase cannot carry the selection, usage, and behavioral burden of a seven-parameter tool.

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 seven optional parameters, no annotations, and no output schema, the description is materially incomplete. It does not explain what the catalog returns, which parameter triggers which behavior, or whether this is a static reference or an active checking tool.

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 seven parameters have descriptions in the input schema, so schema coverage is high and the baseline is 3. The tool description adds no parameter meaning beyond the schema, and it fails to explain why fields like city, feed, or path appear in a tool about HTTP status codes, but it does not mislead about them.

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 identifies the resource domain (HTTP status codes) and says the tool exposes a short catalog, which is more specific than the bare name. However, it uses no action verb and gives no contrast with sibling tools like fetch-status or domain-shape, so an agent cannot tell exactly what invoking the tool does.

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 about when to choose this tool over alternatives such as fetch-status or normalize-url. The schema hints at several possible inputs (url, json, path, etc.), but the description never explains which parameter selects which use case or how they relate to a status-code catalog.

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