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 reveals that external network requests are made, but it does not disclose side effects, response format, error handling, redirect behavior, authentication requirements, or whether failures are surfaced. For a network-mutating tool this is a significant transparency gap.

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, front-loaded sentence with no filler. It conveys the method set and primary capabilities efficiently, and every phrase earns its place.

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?

The tool has five parameters, a nested object, no annotations, and no output schema, so the description needs to explain more than it does. An agent cannot infer what the tool returns, how timeouts surface, or what side effects a request may have. The tool is only partially described for successful invocation.

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 100%, so the baseline is 3. The description confirms that headers and body are supported, but it adds no semantics beyond the schema's field descriptions. It does not clarify body content-type handling, header encoding, or interaction between method and body.

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 states a specific action ('Make HTTP request') and enumerates the supported methods and payload capabilities (headers and body). It clearly identifies the tool's resource without ambiguity and differentiates it from the file, process, memory, and environment siblings.

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 makes the tool's intended use clear: any HTTP request needing method, headers, or body. It does not explicitly name alternatives, but none of the sibling tools serve the same purpose, so no exclusion is necessary. Some guidance on prerequisites or when to prefer this over a shell-based approach would improve it.

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