http_request

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

With no annotations, the description does real work: it discloses that headers are redacted, the body is truncated, and that results are prefixed with PASS/FAIL when assertions are supplied. It omits whether methods are unrestricted, side effects of POST/PUT, and any credential/auth handling, which keeps it from a 5.

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?

Front-loaded with the core action and outputs, then the assertion extras; each sentence carries information. The expect_json path example is dense but earns its space; a brief parameter-completeness pass would cost little.

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-value explanation is rightly omitted, and the assertion semantics are covered. But for a 13-parameter tool with zero schema descriptions, key calling decisions (body vs json_body, verify_tls, follow_redirects) are left unresolved.

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 13 parameters, so the description must compensate. It explains only four of them (expect_status, expect_json with path syntax, expect_contains, max_latency_ms) and leaves the most ambiguous ones—body vs json_body, method, params, headers, timeout, verify_tls, follow_redirects—completely undocumented.

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?

States a specific verb and resource ("Send an HTTP request") plus the reported outputs (status, timing, redacted headers, truncated body). The parenthetical "localhost and private addresses allowed" implicitly separates it from the sibling web_fetch, so an agent can pick between them without opening schemas.

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 localhost/private-address note implies the testing/local reachability use case, and the assertion options hint at smoke-test scenarios. However, it never says when to prefer web_fetch over this tool, nor any preconditions or exclusions.

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