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

There are no annotations and no description of side effects, permissions, or read-only guarantees. Even the tool's output format or potential for errors is unmentioned, offering no transparency about runtime 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 a single short sentence with no unnecessary words, achieving high conciseness. However, the brevity sacrifices clarity about the tool's function.

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 no output schema, no usage context, and parameter descriptions that do not match the tool's purpose, the description is severely incomplete. An agent would have no idea what to pass or what to expect in response.

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 nine parameters have generic descriptions that are entirely unrelated to HTTP status codes (e.g., 'Git ref name,' 'City name,' 'Search text'). These descriptions appear copied from other tools and do not clarify how they relate to the catalog, making them misleading rather than informative.

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 clearly identifies the subject matter but does not specify what action the tool performs (e.g., returns, lists, retrieves). It is a noun phrase rather than a verb phrase, leaving some ambiguity.

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 the many sibling tools (e.g., fetch-status, normalize-url). The description gives no indication of appropriate use cases or contextual triggers.

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