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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It doesn't state whether the tool is read-only, what side effects occur, or what happens to the discarded parameters. The description is silent on all behavioral traits.

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 extremely short but under-specified rather than concise. It lacks structure, has no front-loaded critical information, and does not earn its place because it provides almost no useful content.

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 diverse optional parameters and no output schema, this description is grossly inadequate. It gives no hint of how inputs are used, what the tool returns, or any constraints, making it impossible for an agent to call 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?

Although schema coverage is 100%, the description adds no meaning beyond the individual parameter schemas. It fails to explain how parameters like 'city' or 'json' relate to HTTP status codes, leaving the agent without a coherent understanding of the tool's inputs.

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 the tool is a 'short catalog of common HTTP status codes,' which names a resource but no verb or action. It doesn't say what the tool does with the nine unrelated input parameters (ref, url, city, feed, etc.), nor does it distinguish it from siblings like fetch-status or browser-url-ok. The purpose is vague and not actionable.

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 is provided on when to use this tool versus alternatives. The one-sentence description offers no context, conditions, or exclusions, leaving the agent to guess.

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