http_patch

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing. Mentioning 'using curl' is a minor implementation hint, but there is no statement about mutation side effects, idempotency, whether the body is required, how errors or redirects are surfaced, or what a PATCH does to server state.

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 front-loaded sentence with no filler. It is efficient, though the terseness leaves the gaps above unaddressed rather than earning extra credit.

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?

For an 8-parameter tool with a nested auth object and no output schema, the one-line description is under-specified. It does not describe the response (which the missing output schema would otherwise require) or how the auth configuration actually applies to the request.

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%, including the nested auth object and defaults for timeout, contentType, insecure, and followRedirects. The description adds no syntax or format detail beyond that, so the baseline 3 for a fully documented schema 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 states a specific verb (PATCH) and resource (HTTP request) and names the implementation mechanism (curl). Against a sibling set that is itself a family of HTTP methods (http_get, http_post, http_put, http_delete), the method name alone differentiates it, but the description never explains how PATCH differs from PUT or POST, so sibling routing is inferred rather than stated.

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 when-to-use guidance and no exclusions. An agent gets no help deciding between http_patch, http_put, and curl_custom, and no prerequisites (auth requirements, partial-update semantics versus full replacement) are given.

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