Make HTTP request or download

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

Annotations already provide readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds one meaningful behavioral detail: 'Does not inherit OpenAI or tunnel credentials,' which clarifies security context. However, it omits other traits like rate limits, authentication requirements, or side effects of `saveTo`. The description adds some value beyond annotations but is not comprehensive.

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 extremely concise: two sentences, no filler. Every word serves a purpose, and the core functionality and a key behavioral note (credential isolation) are front-loaded. Despite its brevity, it does not waste space on trivialities.

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's complexity (6 parameters, no output schema, external network interaction), the description is insufficient. It fails to explain return behavior, error handling, how `saveTo` works (path format, overwrite policy), or how `headers` are formatted. The output schema is absent, so the description should provide some return value hints, which it does not. The tool is under-described for reliable agent use.

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 carries the full burden of explaining parameters. It does not mention any of the six parameters (url, body, method, saveTo, headers, timeoutSeconds) or their roles. For example, it doesn't clarify that `method` supports GET/POST/etc., that `headers` expects key-value pairs, or that `body` is used for POST/PUT requests. This is a critical gap for tool selection and correct invocation.

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 the tool's purpose: 'Call an HTTP/HTTPS URL from this PC or download the response to a local file.' This directly specifies the verb (call/download), resource (HTTP/HTTPS URL), and scope (from this PC, with optional file saving). It distinguishes http_request from sibling file and system tools by focusing on network requests.

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 explicit guidance on when to use this tool versus alternatives like exec, open_url, or browser_control. The description only warns about credential inheritance ('Does not inherit OpenAI or tunnel credentials'), which is a behavioral note, not usage context. An agent would need to infer from sibling names that http_request is for raw network calls, but no when-to-use or when-not-to-use information is provided.

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