http_post

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states the action without mentioning response handling, error behavior, redirects, authentication requirements, or side effects. The extensive parameter list (auth, redirects, etc.) is entirely unaddressed.

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 sentence with no fluff, achieving high conciseness. However, it is so minimal that it omits critical context, making it under-specified rather than appropriately concise. It is front-loaded but lacks substance.

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 15 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the purpose of the many body/form/multipart options, auth mechanisms, or how responses are stored (given sibling tools like get_stored_response). An agent would need to rely heavily on parameter names and descriptions.

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 15 parameters have descriptions. The tool description adds no extra meaning beyond the schema, which is acceptable given the high coverage. However, it does not clarify ambiguous parameters like 'auth' versus 'basic_auth' or 'bearer_auth', but the schema descriptions already exist.

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 action 'Make an HTTP POST request' with a specific verb and resource (URL). However, it does not differentiate from sibling tools like http_put or http_patch beyond the method name, so it lacks explicit sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives like http_get or http_put. The description does not mention typical use cases, prerequisites, or exclusions, leaving the agent to infer the purpose.

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