httpreq

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

The description discloses key behaviors such as ECH and DoH enabled by default, support for custom headers and proxies, SSRF protection blocking private IPs, and response truncation. While no response structure is described, the mentioned behaviors are sufficient for a generic HTTP client. No annotations exist to contradict.

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, with no redundant sentences. It front-loads the action and supported methods, then lists features and alternatives efficiently. Every sentence adds 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 the absence of an output schema, the description could mention the expected response structure (e.g., status code, body). However, for a standard HTTP tool, the current level of detail about features, security, and truncation is mostly sufficient. It lacks error handling details but covers core functionality well.

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 coverage is 100%, so the description adds no new parameter information beyond what the schema provides. The description mentions features like ECH and DoH but these are already in the schema. Baseline 3 is appropriate.

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 the tool's purpose: 'Execute HTTP requests with any method' and lists all supported methods. It explicitly distinguishes from sibling tools by advising to use 'webfetch' for fetching web pages and 'download' for file downloads, which effectively differentiates it.

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 states when to use the tool ('Ideal for testing APIs, webhooks, and web services during development') and when not to, by providing alternative tools for related tasks. This gives clear usage guidance.

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