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 behavioral disclosure, yet it is a single 7-word sentence revealing nothing about side effects, prerequisites, or return format. The bizarre parameter set (city, zone, feed) implies behaviors—such as weather, fetch, or validation logic—that are completely unexplained in a tool described as a status-code catalog.

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 front-loaded and short, with no wasted words. However, the brevity is under-specification rather than efficient conciseness—given the drastic mismatch between the stated purpose and the parameters, the description should have bridged that gap, and its terseness actively contributes to confusion.

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 annotations, and no output schema, a one-sentence description is severely insufficient. The description does not explain what the catalog returns, how to invoke it, or why parameters like city, zone, and feed are relevant—all essential context for an agent to call it correctly.

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 schema already documents every parameter's meaning and the baseline is 3. The description adds zero parameter information, which is acceptable for coverage purposes, though the schema descriptions themselves conflict with the catalog framing (e.g., 'discarded after the call' for city).

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 names a specific resource ('catalog of common HTTP status codes') and is not a tautology, which distinguishes it superficially from siblings like fetch-status. However, the stated purpose is disjoint from the actual input schema: all 9 parameters (city, feed, zone, query, ref, host, path, json, url) belong to unrelated domains like weather, validation, and URL normalization, none of which obviously relate to a status-code catalog. This mismatch makes the real purpose genuinely ambiguous to an agent.

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 whatsoever on when to use this tool versus siblings such as fetch-status, browser-url-ok, or web-fetch. No when-to-use, when-not-to-use, or alternative routing is given. The intended selection criteria are left entirely to inference.

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