http_request

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 explain key behaviors such as redirect following, timeout handling, saving to a file, and extracting visible text from HTML, plus it states the return fields (status, headers, body, redirect chain, timing). However, it does not disclose the side effects of methods like POST/PUT/DELETE or how errors/timeouts are reported, leaving some behavioral gaps.

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 compact bullet list of parameters followed by a one-line return specification. The opening sentence states the core purpose, and every line provides necessary information without fluff. It is well-organized and front-loaded with the most important info.

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 there is no output schema, the description appropriately lists return values, including redirect chain and timing. It covers the main parameters and their effects. However, it lacks examples, error-handling semantics, and guidance on how the response body is structured (e.g., JSON vs text), so it is not fully comprehensive for all use 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?

The schema has 0% description coverage, so the description must compensate. It provides a brief gloss for every parameter: url is the target, method lists allowed values, headers/cookies are dictionaries, data is the request body for POST/PUT, follow_redirects defaults to True, timeout is in seconds, save_to files the response, and extract_text strips HTML tags. These explanations add meaning beyond the schema's bare names/types, though some details (e.g., JSON encoding, header merging) remain implicit.

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 opens with a clear, specific action: 'Make an HTTP request and inspect the full response.' It names the resource (URL) and the variety of HTTP methods, making it obvious this is a generic HTTP client. Although it doesn't explicitly distinguish from siblings like http_form_submit, the broad capabilities and method list set it apart from specialized network scanners.

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. The description lists parameters but gives no context about preferred use cases, exclusions, or comparisons with sibling tools like http_form_submit or web_crawl. The user must infer from the generic nature of the tool.

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