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. It does disclose that the tool returns the raw response and makes arbitrary requests, which is useful. However, it does not mention that the response may be truncated or limited by max_chars, nor does it discuss error behavior, redirects, or authentication. These are meaningful gaps for an unrestricted HTTP client.

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 two sentences with no filler. The core function is front-loaded in the first sentence, and the second sentence provides direct routing guidance. Every word earns its place.

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 generic HTTP tool with 5 parameters, no output schema, and no annotations, the description is adequate but incomplete. It clearly explains what the tool does and when to use it, but leaves key invocation details such as response truncation, parameter roles, and error handling entirely to inference.

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%, so the description must compensate for undocumented parameters. It does not mention url, method, body, headers, or max_chars by name or explain their semantics. The phrase 'arbitrary HTTP request' loosely implies method and body flexibility, but max_chars is completely unexplained.

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: 'Make an arbitrary HTTP request and return the raw response.' It also distinguishes itself from fetch_url by noting that fetch_url is preferred for web pages. This clearly separates the tool from its siblings.

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 explicitly says 'Use this for JSON APIs' and provides a direct alternative: 'For reading web pages prefer fetch_url.' This gives an agent a clear decision rule for when to use this tool versus a sibling.

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