termix_hosts_rename_folderRename an SSH hosts folder to update its name and keep credentials organized. Use this action to change folder names for host and credential groups.
Rename folder. Renames a folder for SSH hosts and credentials.
| Name | Required | Description | Default |
|---|---|---|---|
| newName | No | ||
| oldName | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral detail beyond the annotations. It does not mention whether renaming a folder affects existing SSH hosts or credentials, whether it requires permissions, or what happens if the folder does not exist. Annotations already indicate mutating and idempotent, but no additional context is given.
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 very short, consisting of two sentences. The first sentence is a tautology of the title, and the second adds a brief scope. It is concise but lacks substance, making it less useful than it could be.
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 mutation tool with two parameters, the description is incomplete. It does not specify what constitutes a folder, whether the oldName must exist, whether newName must be unique, or what the outcome is. No output schema is provided, so the agent has no information about the result.
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 no descriptions (0% coverage), and the description does not explain the parameters newName and oldName. While their names are suggestive, the description provides no details on format, constraints, or the relationship between them.
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 the verb 'rename' and resource 'folder' and clarifies scope as 'for SSH hosts and credentials', which differentiates from other rename tools like termix_credentials_rename_credential_folder. However, it could be more explicit about how it differs from termix_hosts_update_folder_metadata which might also allow renaming.
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?
No guidance is provided about when to use this tool versus alternatives such as termix_hosts_update_folder_metadata or termix_credentials_rename_credential_folder. The description does not mention prerequisites, side effects, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.