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

The description discloses zero behavioral traits. There are no annotations to cover safety or side effects, and the description itself says nothing about what happens to inputs, what the tool returns, or how it behaves. The only behavioral hints ('discarded after the shape check', 'titles discarded') appear in the schema descriptions, not in the tool description, so they do not satisfy this dimension.

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 extremely short, but this is under-specification rather than effective conciseness. It is a phrase without a verb, contains no actionable instruction, and does not front-load any operational detail that would help an agent invoke the tool. Every other element of the definition must compensate, but none do.

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?

For a tool with 8 parameters, no annotations, and no output schema, a one-sentence noun phrase is completely inadequate. The description leaves all critical context missing: how parameters map to status codes, what the tool returns, whether it is a lookup or a list, and how it relates to sibling tools. An agent cannot correctly select or invoke it based on this description.

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 8 parameters have individual schema descriptions, so schema coverage is 100%, which gives a baseline of 3. The tool description, however, adds no meaning beyond the schema and even fails to explain how parameters relate to the stated purpose of an HTTP status catalog. It does not compensate for the apparent mismatch between the description and the parameter set.

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 a noun phrase, not a verb+resource: 'Short catalog of common HTTP status codes' states what the tool contains but not what operation it performs or returns. The input schema parameters (ref, url, city, feed, host, json, path) are entirely unrelated to HTTP status codes, creating confusion about actual purpose. It does not distinguish from siblings like fetch-status or normalize-url.

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 alternatives. No context, no when/when-not conditions, and no mention of which of the 8 parameters are relevant or how to choose among them. The description gives no hint about the intended use case.

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