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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says it's a catalog, implying a read-only reference, but doesn't mention that many parameters are discarded, that it performs no network calls, or what the output format is. There is no contradiction, but the description leaves the tool's behavior largely unspecified.

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 with no waste, but it's under-specified for a tool with 9 parameters and no annotations. It lacks critical information about behavior, use cases, or parameter roles, so the brevity works against clarity rather than enhancing it.

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?

Given the tool's complexity (9 optional parameters, no output schema, no annotations), the description is woefully incomplete. It doesn't explain what the tool actually does with the inputs, what it returns, or how it relates to the catalog of status codes. An agent has almost no basis to invoke this tool 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?

The schema covers all 9 parameters with individual descriptions, but the tool description doesn't connect them to the catalog's purpose. The parameters (ref, url, city, feed, host, json, path, zone, query) seem unrelated to HTTP status codes, and the description offers no explanation of how they are used or why they matter. This creates confusion rather than adding semantic value.

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 it's a catalog of HTTP status codes, which gives a basic idea of the resource, but it doesn't specify what operations it supports (lookup, list, explanation) or how it differentiates from siblings like fetch-status or browser-url-ok. It's not a tautology, but it's vague and doesn't help an agent decide when this is the right tool.

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 any of the 27 siblings. It doesn't mention typical use cases, prerequisites, or alternatives. An agent would have to infer when a 'short catalog' is needed, and the description gives no explicit or implicit direction.

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