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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'catalog' implying a static reference, but the schema parameter descriptions (e.g., 'discarded after the shape check', 'no disk access') suggest the tool performs various checks. The description is silent on these behaviors and is effectively misleading about the tool's operations.

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 a single concise sentence, but it is under-specified and fails to convey essential information about parameter usage or behavior. Conciseness is achieved at the expense of clarity, so it is adequate but not helpful.

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 9 parameters, no required fields, no output schema, and no annotations, the description is grossly incomplete. It does not explain what the parameters are for, how the catalog is queried, or what the tool returns. An agent has no basis to construct a correct invocation.

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 all 9 parameters have individual descriptions. The tool description adds no information about how these parameters relate to the catalog or how they are used. It does not compensate for the gap between the stated purpose and the parameter set, but the schema itself documents each parameter, so a baseline of 3 is appropriate.

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 states a clear purpose ('Short catalog of common HTTP status codes') with a specific noun, but it does not distinguish this tool from siblings like fetch-status or validate-json, and the parameter schema (9 unrelated fields like url, json, path) does not align with the stated purpose, creating ambiguity about what the tool actually does.

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 provided on when to use this tool versus alternatives. It does not mention any conditions, alternatives, or exclusions. An agent cannot determine when to select this tool over fetch-status or validate-json from the description alone.

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