kinsta_environments_ssh_generate-passwordGenerate a new SSH/SFTP password for a Kinsta environment by providing its ID, replacing the existing password with a secure one for immediate use.
Generate a new SSH/SFTP password for an environment.
| Name | Required | Description | Default |
|---|---|---|---|
| env_id | Yes | The environment ID |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The only annotation is openWorldHint=true, signaling a mutation, but the description does not disclose the side effects: whether it overwrites the current password, how the new password is returned, or any prerequisites like existing SSH configuration. It adds no behavioral context beyond the name.
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 with no filler, front-loading the action and resource. It is concise and well-structured, though brevity borders on under-specification.
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 mutation side effect and the cluster of SSH-related sibling tools, this description is inadequate. It omits what happens to the existing password, how the new password is delivered, and any prerequisites or rate limits. An agent cannot safely invoke it without additional information.
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 fully documents the single parameter env_id with a clear description. The tool description adds nothing extra about the parameter, so the baseline score of 3 applies because schema coverage is 100%.
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?
States a specific verb (Generate) and resource (new SSH/SFTP password) for an environment. The word 'new' implies a creation action that distinguishes it from read-only tools like kinsta_environments_ssh_password, but it does not explicitly name the alternative or clarify the distinction further.
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?
Provides no guidance on when to use this tool versus related SSH tools such as kinsta_environments_ssh_status, kinsta_environments_ssh_password, or kinsta_environments_ssh_password-expiration. The agent must infer usage context from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.