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

With no annotations, the description must disclose side effects or state changes, but it only states 'short catalog' with no indication of read-only behavior, data mutation, or external effects.

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 concise but overly sparse, consisting of a single vague noun phrase. It does not structure any useful information about the tool's behavior 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?

With 9 parameters and no output schema, the description should clarify what the tool does with the inputs. It provides none of this context, leaving the tool's purpose and inputs entirely unexplained.

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 schema descriptions (e.g., 'Git ref name', 'URL', 'City name') appear completely unrelated to 'HTTP status codes' and do not explain how any parameter contributes to the catalog. The tool description provides zero mapping between parameters and purpose.

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 names a resource (HTTP status codes) but lacks an explicit verb, making it unclear whether the tool lists, looks up, or validates codes. It is not a tautology, but the intended operation is ambiguous.

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 guidance is given on when to use this tool versus alternatives like fetch-status or web-fetch. The description does not mention any distinguishing scenarios or conditions.

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