connections_drop_connections

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about permissions, irreversibility, or the confirm-gate that determines whether the request is actually sent. "Drop" implies a mutating, destructive action, but the description never confirms or qualifies that.

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?

It is short and front-loaded, but the leading HTTP route and trailing "Tags: Connections Controller" are boilerplate that costs space without adding agent-relevant meaning. The one substantive sentence is buried under that noise.

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 a destructive two-parameter tool with no annotations and no output schema, the description should cover what happens on execution and the confirm behavior. Instead the confirm semantics live only in a Russian-language schema description, and the tool description explains nothing about outcomes or auth.

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 50%, and the nested union members (dropBy, targetNodes) already carry their own descriptions, so the schema does much of the work. The description's "for Users or IPs" loosely maps to the dropBy union but adds no syntax, defaults, or clarity about the confirm parameter.

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 line "Drop Connections for Users or IPs" gives a verb and resource, but "drop" is never explained (terminate active sessions vs. remove records) and the definition is padded with a raw REST route and tag metadata. It does not distinguish this tool from the read-only connections siblings (connections_by_user, connections_by_node).

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 statement of when to use this tool versus alternatives, no prerequisites, and no mention that a confirmation flag exists. The only hint of scope is the phrase "for Users or IPs," which implies targeting but gives no usage guidance.

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