delete-connections-username

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

Annotations confirm it is a write operation (readOnlyHint=false). The description adds the destructive action of closing connections and an optional reason, but does not disclose potential side effects, reversibility, or required permissions. With annotations already indicating non-read-only, the description provides no additional critical behavioral context.

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 concise, consisting of one declarative sentence and a fragment. However, it is front-loaded and contains no filler. It earns its place without being overly terse, though a slightly richer description could better fit the context.

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 the simple 2-parameter schema and no output schema, the description covers the basic operation. However, it uses 'close' while the tool name is 'delete-connections-username', which could cause confusion about whether connections are closed or permanently deleted. No information about return values or confirmation is provided, leaving the agent uncertain about the outcome.

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%; the description only mentions 'Optionally provide a reason' without explaining the purpose or format of either parameter. It does not clarify that 'username' identifies the user whose connections are to be closed, or how 'reason' is used (e.g., logging, audit). The minimal addition of 'Optionally provide a reason' is insufficient to compensate for the lack of schema descriptions.

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 ('Close all connections'), target ('for a specific username'), and optional parameter ('reason'). It effectively distinguishes from siblings like 'delete-connection' (single connection) and 'list-connections-username' (listing, not deletion).

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?

The description provides no explicit guidance on when to use this tool versus alternatives (e.g., 'delete-connection' for single connections). It implies bulk cleanup by username but lacks when-not-to-use or prerequisite information.

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