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

No annotations are provided, so the description carries the full burden of disclosing side effects, auth requirements, rate limits, or return behavior. It states none of these, and for a tool with 9 parameters, the absence of any behavioral information is a significant gap.

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 in length but not in information value. It under-specifies the tool to the point of being unhelpful, failing to earn its place by conveying any actionable detail. Front-loading is irrelevant when the content is a tautology.

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 required fields, no output schema, and no annotations, the description is completely inadequate. An agent cannot determine what to pass in, what the tool returns, or how it fits into a workflow. The sibling context includes similar tools like 'fetch-status', but the description gives no differentiation.

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 input schema provides descriptions for all 9 parameters (100% coverage), so the baseline is 3. However, the tool description does not connect these parameters to the 'catalog of status codes' concept—there is no 'code' parameter, and the parameters like 'city' and 'zone' seem orthogonal. The schema descriptions themselves are generic ('City name for a public weather hint') and don't explain how they relate to the tool's stated purpose, so the description adds no value beyond the schema.

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' merely restates the tool name and provides no verb or resource. It doesn't specify whether the tool returns a code, lists codes, or validates a code, leaving the agent uncertain about its primary function. The presence of unrelated parameters like 'city' and 'zone' further muddles the purpose.

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 siblings such as 'fetch-status' or 'web-fetch'. The description does not mention any context, alternatives, or exclusions, leaving the agent to guess which tool fits a given scenario.

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