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. It fails entirely: it doesn't state whether the tool makes network requests, performs validation, or returns a status code. The parameter descriptions in the schema mention 'discarded after the shape check' and 'no disk access', but these are in the schema, not the description. The description offers no insight into side effects, input handling, or return behavior.

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 in length (one sentence), but it is under-specified rather than appropriately concise. For a tool with 9 parameters, a one-sentence description that omits all functional detail is not acceptable conciseness; it's a deficiency. The structure is fine, but the content is insufficient.

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 the complexity (9 optional parameters, no output schema, no annotations), the description is grossly incomplete. It doesn't explain what the tool does with the inputs, what it returns, or how it relates to the catalog. An agent cannot call this tool correctly without additional knowledge. The description fails to provide any operational context.

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 is 100%, so each parameter has a description. The baseline for high coverage is 3. The description adds no additional meaning beyond the schema; it doesn't mention how parameters influence the result. The schema descriptions themselves provide some semantics (e.g., 'discarded after the shape check'), but these are part of the schema, not the tool description. The description contributes nothing to parameter understanding.

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 'Short catalog of common HTTP status codes' is a noun phrase that states what the tool is, not what it does. It lacks a verb (e.g., 'returns', 'lists', 'provides') and gives no indication of how the 9 input parameters relate to the catalog. It does not distinguish itself from siblings like fetch-status or browser-url-ok, which are clearly about checking status. The name 'status-catalog' suggests a reference, but the parameters imply some checking behavior, creating ambiguity.

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. The description never mentions any sibling tool, use case, or exclusion criteria. An agent cannot determine whether this should be used instead of fetch-status, domain-shape, or any other status-related tool. The description is a single sentence with no context.

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