ssh_password_delete

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

Annotations already flag destructive behavior, but the description adds meaningful details: it removes the password from the OS credential helper, removes the RunBeacon profile reference, and rejects passwordless SSH profiles. This goes beyond the annotations and explains actions and constraints.

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 a single sentence that is front-loaded with the action and resource, followed by essential behavioral details. Every phrase earns its place with no redundancy or filler.

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 simple one-parameter destructive tool with no output schema, the description fully covers what will happen (deletion from OS helper and profile reference), the precondition (created via ssh_password_save), and an important constraint (passwordless profiles rejected). No return format is necessary given the lack of output schema.

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 already provides 100% coverage for the single required parameter 'id' with a clear description. The description adds that passwordless profiles are rejected, which is relevant but not directly about parameter format. The baseline of 3 is appropriate given complete schema coverage.

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 states a specific action ('Delete') on a specific resource ('SSH password created through ssh_password_save') and clearly distinguishes the scope by mentioning the source and the additional removal of the RunBeacon profile reference. This makes it distinct from broader deletion tools like credential_profile_delete.

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 clearly implies this tool is for deleting SSH passwords created via ssh_password_save, providing context for when it applies. However, it does not explicitly name alternative tools or state when not to use it, which would have warranted a 5.

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