ssh_generate_rdp_bootstrap

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

With no annotations, the description carries the full burden. It transparently discloses the core behavior (generates a PowerShell install script), but doesn't elaborate on how the host and userType parameters shape the script, or whether the script triggers side effects like firewall changes or reboots. Some secondary behavioral details remain opaque.

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, front-loaded sentence with zero redundancy. Every word adds information: the action ('Generate'), the format ('1-liner PowerShell script'), the delivery channel ('copy-paste into RDP'), and the goal ('install OpenSSH server').

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 description covers the essential output and purpose for a simple generation tool with no required parameters and a rich schema. It doesn't explicitly explain how this tool fits into the broader SSH workflow (e.g., enabling later ssh_* operations), but that is inferable from sibling names and the stated goal.

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 high coverage (100%), with clear descriptions for both parameters: host as 'Target host IP or hostname' and userType as an enum with admin/user meanings. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 uses a specific verb ('Generate') and resource ('1-liner PowerShell script to install OpenSSH server'), clearly distinguishing it from sibling tools that test connections, execute commands, or transfer files. The 'RDP session' context further pinpoints the exact workflow.

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 states the usage context: copying the script into an RDP session to bootstrap OpenSSH on a Windows target. It doesn't explicitly list alternatives or when not to use, but the purpose is distinct enough from siblings that no further exclusion is needed.

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