http_post

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

With no annotations, the description carries the full burden, and 'using curl' is the only behavioral hint (implying a subprocess-based request). It says nothing about return format, error handling, timeout/redirect defaults, or what happens with the insecure flag, all of which matter for an HTTP client tool.

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 is concise and front-loaded, with no wasted words, but for a tool with 8 parameters and a nested auth object it is arguably under-specified rather than efficiently concise.

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 8 parameters, a nested auth configuration, no annotations, and no output schema, a one-line description leaves too much unexplained. An agent gets no help on return values, error behavior, or how the auth object should be populated.

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 all 8 parameters including the nested auth object are documented in the schema itself. The description adds no parameter meaning beyond that, making the baseline 3 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 states a specific verb and resource ('HTTP POST request'), which is clearer than the bare name, but it largely restates the tool name http_post and adds no differentiation from siblings such as http_put or http_patch beyond the implied method.

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 use this tool versus the many siblings (http_get, http_put, http_patch, curl_custom, etc.), no mention of prerequisites, and no exclusions. The agent must infer everything from the method name.

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