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

With no annotations, the description carries the full burden of behavior disclosure. It reveals nothing about side effects, return format, or what happens to inputs. The parameters (ref, url, city, etc.) are not tied to the stated purpose, creating confusion about actual behavior.

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 one short sentence, but it's under-specified rather than concise. It lacks any useful structure or front-loaded key information. It's a stub, not a concise specification.

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 output schema, and no annotations, the description is severely incomplete. It doesn't explain the tool's operation, output, or relationship between parameters and the stated catalog purpose. An agent cannot confidently invoke it.

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 baseline is 3, but the description adds no value and actually conflicts semantically – the parameters (ref, url, city, feed) have no obvious relation to an HTTP status code catalog. The description fails to bridge schema parameters to the stated purpose.

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') but lacks a verb – it doesn't state what the tool does with them (return, validate, list). It also doesn't differentiate from siblings like fetch-status or normalize-url. The purpose is vague and disconnected from the nine parameters.

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 on when to use this tool versus alternatives. There is no mention of context, conditions, or exclusions. An agent would have no idea when to pick this over the many sibling tools.

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