http_delete

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

No annotations are provided, so the description carries the full behavioral burden. It only notes the underlying implementation ('using curl') and says nothing about destructive semantics, whether a request body is supported, auth requirements beyond the schema, or what the response looks like, which is a notable gap for a DELETE operation.

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?

A single short sentence with no wasted words, and it is front-loaded with the core purpose. It is efficient, though the brevity borders on under-specification rather than being optimally informative.

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?

With 6 parameters, a nested auth object, no annotations, and no output schema, this tool needs more descriptive context than one sentence. The description omits destructive/irreversibility disclosure, auth flow explanation, and response behavior, leaving it inadequate for the tool's complexity.

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%, with each parameter (url, auth, headers, timeout, insecure, followRedirects) documented inline, so the schema does the heavy lifting. The description adds no parameter meaning beyond that, matching the baseline of 3.

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 HTTP verb and resource ('HTTP DELETE request'), making the operation unambiguous and implicitly distinguishing it from the http_get/http_post/http_put/http_patch siblings. It does not, however, explicitly name which sibling to prefer or when, so it falls short of a 5.

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?

There is no guidance on when to choose this tool over http_post, http_put, http_patch, or curl_custom, nor any prerequisites or exclusions. The reader is left to infer usage purely from the HTTP method name.

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