node_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 behavioral burden and largely drops it. For an arbitrary outbound network primitive it says nothing about what is returned (status, body, headers), timeout or failure behavior, redirect handling, credential/header propagation, or the security implications of insecure_tls — all of which matter for safe invocation.

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?

A single front-loaded sentence with the action and scope stated immediately and no filler. Its brevity is appropriate in form, though it reflects under-specification rather than disciplined economy.

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?

For a 6-parameter tool with a nested headers object, no annotations, and no output schema, the description is too thin. An agent cannot tell what the call returns, whether failures surface as errors, or how insecure_tls should be used, leaving key invocation decisions unaddressed.

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?

With only 33% schema description coverage across 6 parameters, the description needs to compensate but largely does not. 'From inside a TargetNode' does clarify that node identifies the host executing the request, but method, body, headers, and insecure_tls receive no explanation beyond their bare names and defaults.

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 verb and resource ('Perform an HTTP/HTTPS request') and adds meaningful scope: the request originates 'from inside a TargetNode' and is aimed at inspecting internal services. This distinguishes it conceptually from siblings like node_exec or node_read_file, though those alternatives are not named explicitly.

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 when-to-use vs when-not guidance and no mention of alternatives such as node_exec, which could also be used to reach an internal service. The phrase 'to inspect internal services' hints at intent but gives no conditions, prerequisites, or exclusions an agent could act on.

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