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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it discloses nothing: no side-effect profile, no read-only guarantee, no mention that inputs are discarded, and no return behavior. The word 'catalog' weakly implies a static reference, but that is not explicit.

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 short, but brevity here comes at the expense of substance. It provides no structure, no front-loaded action, and leaves an 8-parameter tool almost completely unexplained. This is under-specification rather than effective conciseness.

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?

The tool has eight diverse parameters, no annotations, and no output schema, yet the description only says it is a 'short catalog'. An agent cannot determine what input to provide, how the parameters relate to the catalog, or what the tool will return. This is far from complete.

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?

Schema description coverage for the eight parameters is essentially 100%, so the baseline is 3 even though the tool description adds no parameter meaning. The schema descriptions such as 'discarded after the shape check' and 'HTTPS URL to normalize or cite' are individually clear, but the description does not connect them to the catalog 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 is essentially a noun phrase restating the tool name: 'Short catalog of common HTTP status codes' matches 'status-catalog' almost word-for-word. It lacks a specific verb like 'returns' or 'lists', and gives no hint of what the eight input parameters have to do with the catalog.

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 on when to use this tool versus siblings like fetch-status, domain-shape, or validate-json. No conditions, exclusions, or alternative tool names are mentioned.

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