game_http_request

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the HTTP verbs and payload options found in the schema; it does not mention that the tool makes an external network call, can trigger side effects on remote servers, or what the response contains.

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 a single, front-loaded sentence with no filler. Every word contributes meaning by enumerating supported methods and capabilities.

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 that there is no output schema, no annotations, and a tool that can issue arbitrary network requests, the description is too sparse. It does not explain what the tool returns, how errors/timeouts surface, or that methods like POST/PUT/DELETE may modify remote resources.

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 100%, so the input schema already documents all five parameters. The description adds no semantics beyond what the schema provides—it simply names headers and body, which are already described as key-value pairs and body string respectively.

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 names a concrete action (performing HTTP requests) and the supported verbs (GET/POST/PUT/DELETE), along with headers and body. This clearly distinguishes it from the sibling game_* tools, none of which are general-purpose HTTP clients.

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 intended use—making HTTP requests with a URL and optional method/headers/body—is implied by the description but never stated explicitly as 'use this when...' It does not mention alternatives like game_websocket or game_rpc, nor does it give exclusions for when plain HTTP is not appropriate.

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