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

There are no annotations, so the description must carry the full burden of disclosing behavior. It only says 'short catalog' and gives no indication of validation, normalization, discarding inputs, or what happens on success/failure. The schema hints at these behaviors through parameter descriptions, but the description itself adds nothing behavioral.

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 short sentence, which is concise, but it under-specifies the tool's functionality to the point of being unhelpful. It does not front-load any actionable details beyond a vague catalog claim, and the mismatch with the schema makes it misleading rather than efficient.

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?

With 9 parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain what the tool actually does with the inputs, what output it produces, or any side effects. An agent cannot confidently call this tool correctly based on the provided description alone.

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?

The schema descriptions cover 100% of the parameters and each is fairly explanatory (e.g., 'Git ref name; discarded after the shape check'). The description adds no parameter-specific info, but since schema coverage is complete, the baseline of 3 is appropriate. It neither improves nor harms 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 states 'Short catalog of common HTTP status codes,' which implies a reference tool, but the schema lists a heterogeneous set of parameters (ref, url, city, etc.) that are each described as being discarded after a shape check or similar. This is a misleading mismatch between description and schema, so an agent could easily pick the wrong tool. It does not specify a clear verb or resource that matches the schema's behavior.

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 given on when to use this tool versus alternatives. The description does not mention any context, exclusions, or relational info to sibling tools. An agent has no basis to decide whether this is the right tool for a given task.

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