browser_http_get

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

With no annotations, the description carries the full burden of behavioral disclosure. It does state that the tool is browser-less and returns the response body, which are meaningful behavioral traits. However, it does not mention how non-2xx responses are handled, whether redirects are followed, or the effect of the timeout parameter—leaving notable gaps for a network call.

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 two short sentences with no filler. The core action and result are front-loaded, and the optional header detail is presented right after. Every word earns its place, and the structure makes the tool easy to scan.

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 simple GET tool with no annotations and no output schema, the description covers the basic purpose and result but falls short on critical context. The timeout parameter is entirely unexplained, and error/redirect behavior is absent. The description is not complete enough for an agent to use the tool confidently in edge cases.

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?

Schema description coverage is 0%, so the description must compensate for all parameters. It explains headers well ("Optional `headers` dict for authentication or custom request headers"), but it entirely omits the timeout parameter, including its units and meaning, and url is left to be inferred. This is insufficient for a tool with three undocumented parameters.

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 clearly states a specific verb and resource: "HTTP GET `url` (browser-less)" and names the result ("Returns the response body"). The "browser-less" qualifier distinguishes it from the browser-navigation siblings like browser_goto and browser_js, leaving no ambiguity about what this tool does.

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?

The description implies usage context by saying "browser-less", signaling that this is for raw HTTP requests without a browser, but it never explicitly names alternatives or states when not to use it. An agent can infer the when, but it lacks the direct routing that would earn a 4 or 5.

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