Remove SFTP User

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

The destructiveHint and openWorldHint annotations already signal the destructive nature, and the description adds context about the target scope ('additional SFTP/SSH user', 'from an environment'). However, it does not disclose whether removal is reversible, affects active sessions, or has other side effects expected of an open-world destructive action.

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 one sentence with no filler; the verb is front-loaded and the resource/scope qualifiers are meaningful. It is appropriately minimal for a single-parameter destructive action.

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 single-parameter remove operation with destructive annotations and no output schema, this is nearly complete: the agent knows what is removed and required inputs. The only real gap is operational context, such as retrieving the account ID via sftp-users_list before removal.

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?

The input schema already documents the single sftp_account_id parameter with 100% coverage, so the description need not add parameter syntax. It adds no extra guidance on ID format or how to obtain the ID, but the schema covers the core semantics.

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 names a specific operation ('Remove') and a precise resource ('additional SFTP/SSH user account'), and scopes it to an environment. This makes it clearly distinguishable from the related sftp-users_list, sftp-users_toggle, and sftp-users_add siblings.

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 verb and resource make the intended use inferable, but the description gives no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives such as sftp-users_toggle for disabling an account or sftp-users_list for locating the account ID.

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