connections_drop

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is partially covered by structured data. But for a destructive operation that terminates live sessions, the description says nothing about impact (immediate disconnect of active users/IPs), reversibility, or scope of effect, leaving a meaningful gap.

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 with the action, so there is no wasted text. However, this brevity stems from under-specification rather than disciplined concision, so it does not earn a high score.

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 a two-parameter, destructive, nested-schema tool with no output schema, the description is far too thin. It omits when to use it, what the parameters mean, and what the destructive action actually does, leaving the agent to infer nearly everything from the schema alone.

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 0% and the description mentions only 'Users or IPs' generically, with no explanation of the dropBy / targetNodes oneOf branches. The nested schema consts (allNodes, specificNodes, userIds, ipAddresses) carry most of the meaning, and the description adds nothing beyond the users/IPs mention.

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 phrase 'Drop Connections for Users or IPs' gives a verb (drop) and resource (connections) and hints at the two targeting modes (users/IPs). However, it reads as a title fragment rather than a stated purpose, and it does not differentiate itself from the read-side siblings like connections_by_user_result or connections_by_node_result beyond the word 'drop'.

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 sibling connection-lookup tools, no prerequisites, and no warning about the destructive action. The only usage cue is the imperative verb 'Drop', which an agent must interpret on its own.

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