send_http_request

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention potential side effects (e.g., sending data to external servers, network access requirements, timeouts, or error handling), leaving the agent without a clear safety/profile picture.

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, compact sentence that gets straight to the point. It front-loads the verb and resource and includes the key customization features without any fluff.

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 description lacks information about the response format or return value, which is significant given the absence of an output schema. It also omits details about error conditions or limitations, making it incomplete for an agent to fully anticipate the tool's behavior.

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 description mentions custom headers, query parameters, and body, which aligns with the schema, but doesn't add syntax or format details. Since the schema already documents all parameters with 100% coverage, the description provides minimal additional value beyond a high-level summary.

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 function: sending an HTTP request to any endpoint, listing the key customization options (headers, query params, body). It uses a specific verb and resource, and with no sibling tools, there is no need for differentiation.

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 the tool is for general HTTP requests but provides no explicit guidance on when to use it versus alternatives, nor any exclusions or prerequisites. Given the lack of sibling tools, the usage context is only implied.

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