automation_http_request

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

No annotations are provided, so the description carries the full burden; to its credit it discloses two real behaviors the agent could not otherwise know: private/internal hosts are blocked by default, and response bodies are truncated. It omits error behavior, redirect handling, retry semantics, and whether json_body and body interact, which matters for a network tool with zero annotation coverage.

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?

Three short sentences, front-loaded with the action and methods, then the two most surprising constraints. Nothing is padded, though the terseness leaves known ambiguities unresolved.

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?

An output schema exists, so return values need not be described. But for a six-parameter network tool with no annotations and no schema descriptions, the definition leaves the two body parameters indistinguishable and the timeout unexplained — the agent cannot invoke it confidently without guessing.

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% across six parameters, so the description must compensate and largely does not. It explains the method set and that the body may be truncated, but says nothing about headers, timeout units/defaults, or the critical distinction between body and json_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 gives a specific verb and resource ('Perform an HTTP request') and enumerates the supported methods, which is enough to distinguish it from pure utility siblings such as automation_uuid4 or analysis_math_eval. It does not, however, differentiate itself from automation_send_webhook, which is the closest overlapping sibling.

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?

Listing the methods implies this is the general-purpose HTTP escape hatch, and the anti-SSRF note implies an internal-network exclusion. There is no explicit statement of when to prefer this over automation_send_webhook, nor of any prerequisites such as auth or rate limits.

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