http_request

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

No annotations are provided, so the description carries full burden. It discloses auto-serialization for JSON, handling of raw payloads, and return fields (status, headers, body, elapsed time). However, it omits error handling, authentication, rate limits, or potential side effects (though HTTP requests are generally idempotent).

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 concise, front-loading purpose, then detailing parameter usage, scope, and return format. No redundant sentences, every sentence adds unique value.

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?

Given 7 parameters, no output schema, and no annotations, the description covers key behavioral aspects: method support, payload types, network scope, and return shape. Lacks error/security details but is sufficient for typical use.

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 0% schema description coverage, the description must compensate. It explains the difference between body and body_json, which are the most semantically nuanced parameters. However, other parameters (url, method, headers, timeout_ms, max_bytes) rely solely on schema metadata. The description adds value but not exhaustive.

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 it is a universal HTTP client performing all major methods (GET, POST, PUT, etc.), and distinguishes itself from the sibling tool fetch_text by indicating broader functionality.

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?

Provides explicit guidance on when to use body_json vs body for different payload types, and mentions compatibility with various network addresses. Lacks explicit exclusions or comparison to fetch_text, but context is clear.

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