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

No annotations are provided, so the description must carry the full behavioral burden, but it reveals nothing about whether this is a static lookup, a network call, or how the parameters affect behavior. The schema hints that many parameters are discarded, but the actual operation and return format are undisclosed.

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 phrase with no wasted words, which is concise, but it is under-specified to the point of being a fragment. It prioritizes brevity over actionability, so it is only minimally adequate.

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?

The tool has no annotations, no output schema, and a seven-parameter input schema that appears unrelated to the stated purpose. The description fails to explain return values, side effects, or how the parameters are meant to be used, making the definition inadequate for 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?

All seven parameters have explicit schema descriptions, so schema coverage is effectively 100%, which sets a baseline of 3. The tool description adds no parameter-level insight, and the relationship between parameters like city, json, and feed and a status-code catalog is unexplained, but the high schema coverage prevents a lower score.

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 resource (common HTTP status codes) and labels it a catalog, but it lacks a verb such as 'returns' or 'lists' and reads as a noun phrase rather than an action statement. It does not clearly differentiate this tool from siblings like fetch-status or web-fetch.

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 provides no guidance on when to use this tool versus any of the sibling tools. There are no context cues, exclusions, or alternative references, so an agent has no basis for selecting this tool.

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