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, and it discloses almost nothing: no indication of what the catalog returns, whether inputs filter or look up entries, or whether the operation is read-only. The schema's parameter descriptions ('JSON text to validate; discarded after the check') imply behaviors that contradict the description's stated purpose of an HTTP status-code catalog, leaving an internally inconsistent picture.

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 contains no filler and is front-loaded with the core topic, which is efficient. But it is a fragment that under-specifies a 4-parameter, zero-annotation tool — brevity is achieved at the direct expense of the detail this tool needed, so it is barely minimally appropriate in size.

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 no annotations and no output schema, the description must carry the explanatory load, and the one-line noun phrase covers nearly none of it: expected return value, how the four parameters map to the catalog, side effects, and sibling differentiation are all absent. An agent cannot reliably determine how to invoke this tool correctly from the information provided.

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 coverage is 100%, so the baseline is 3: each parameter has a clear one-line description that conveys its literal meaning. However, the tool description adds no parameter semantics at all, and the schema's parameter descriptions appear to be lifted from sibling tools rather than tied to a catalog of HTTP status codes, creating cohesion confusion about why these inputs exist together.

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 verbless noun phrase — 'Short catalog of common HTTP status codes' — that essentially restates the tool name 'status-catalog' and never states an operation the agent can invoke. Worse, the stated purpose (HTTP status codes) has no visible connection to the four parameters (url, host, json, zone), so an agent reading the description cannot tell what calling this tool actually does. It also fails to differentiate the tool from its siblings, whose parameters it appears to borrow.

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?

The description offers no guidance on when to use this tool, no exclusions, and no mention of alternatives such as url-normalizer, validate-json, or timezone — even though the parameters plainly overlap with those sibling tools. An agent deciding between status-catalog and a sibling when given a URL or JSON input gets no help resolving the ambiguity.

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