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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it reveals nothing about side effects, return values, or how inputs are processed. The schema hints at normalization/validation/discarding, yet the description is silent on behavior, so an agent cannot anticipate the tool's actions.

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, which is concise but severely under-specified. It lacks any structure or front-loaded information that would clarify the tool's operation or distinguish it from siblings, making the brevity counterproductive rather than efficient.

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 has 4 parameters, no output schema, and no annotations, the description is grossly insufficient. It fails to explain what the tool does with the inputs, what results to expect, or how it relates to HTTP status codes, leaving an agent with virtually no contextual information to invoke it 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?

While schema description coverage is 100%, the parameter descriptions (e.g., 'HTTPS URL to normalize or cite', 'JSON text to validate') suggest functionality unrelated to HTTP status codes. The tool description adds no explanatory value for these parameters and instead conflicts with the schema's apparent intent, failing to help an agent map inputs to the tool's 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 'Short catalog of common HTTP status codes' states what the tool contains but not what it does with the provided parameters (url, host, json, zone). There is no clear verb-resource relationship that connects these inputs to the stated purpose, making the tool's actual function ambiguous and inconsistent with its schema.

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 given on when to use this tool versus siblings like normalize-url, validate-json, or timezone. The description does not mention conditions, exclusions, or alternatives, leaving an agent without any basis to select this tool appropriately.

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