ssh_remove_passwordless

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

With no annotations, the description carries the full burden. It discloses the primary destructive behavior (removing keys/clearing all) and consequence (revoking passwordless login), but doesn't mention authentication prerequisites, lockout risks, or reversibility.

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?

One sentence that conveys the action and scope efficiently without wasted words. It front-loads the primary function.

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?

The tool has 8 parameters and no output schema, and the description is minimal. It doesn't explain authentication prerequisites or failure modes, though the schema covers parameter semantics. It's sufficient for a straightforward revocation tool but lacks deeper behavioral context.

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 schema has 100% coverage for parameter descriptions, so the baseline is 3. The description adds no specific parameter details beyond what's in the schema, but it does align the 'remove specific key' vs 'clear all' options with keyPathToRemove and removeAllKeys.

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 tool's action ('Remove public key entry or clear ALL keys from authorized_keys') with specific resource and purpose, distinguishing it from siblings like ssh_setup_passwordless and ssh_clear_known_hosts.

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 implies the usage context (revoking passwordless SSH login) and clearly differentiates the two modes (specific key vs all keys). It doesn't explicitly name alternatives, but the tool's function is self-evident in context.

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