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

No annotations are present, and the description does not disclose side effects, read-only behavior, or output format. The input schema includes many unrelated parameters described as 'discarded', which further obscures the 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 a single concise sentence and not verbose. However, it is too minimal to convey the tool's purpose and usage, making the brevity a weakness rather than a strength.

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 annotations, and a confusing set of seemingly irrelevant parameters, the description is incomplete. An agent cannot determine what arguments to provide or what result to expect.

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 every parameter has a description, those descriptions (e.g., 'Git ref name; discarded after the shape check') are unrelated to an HTTP status-code catalog. The semantics are misleading and provide no meaningful guidance for invoking this tool.

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 ('catalog of common HTTP status codes') but lacks an explicit verb or precise action. It is unclear whether the tool returns a list, looks up a code, or validates a status, so an agent cannot confidently select it.

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 alternatives such as fetch-status or browser-url-ok. No conditions, exclusions, or contextual triggers are provided.

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