Create a folder

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

Annotations already indicate this is a non-read-only, non-idempotent, non-destructive operation. The description adds the useful context that the folder is created 'on the remote host' and emphasizes it is 'new,' implying no overwrite. However, it does not disclose failure behavior, parent-directory requirements, permissions, or effects if the folder already exists.

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 short but contains a redundant opening sentence that simply repeats the title. The meaningful content is in the second sentence, but the first sentence does not earn its place. It is under-specified rather than efficiently compact.

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?

With three undocumented parameters, no output schema, and no usage guidance, this description is far from complete. An agent cannot reliably determine how to construct a valid call, especially since no parameters are marked required. The description works as a label but not as a standalone tool contract.

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?

Schema description coverage is 0%, and the description does not explain any of the three parameters: path, sessionId, or folderName. It is left ambiguous whether path is the parent directory, whether folderName is a relative name, or how sessionId selects the remote host. The description adds no parameter-level meaning.

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 clear action and resource: 'Creates a new folder on the remote host.' This distinguishes it from sibling file tools like termix_files_create_file, since the resource type is explicit. The first sentence 'Create a folder' is redundant with the title, but the second sentence provides concrete meaning.

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 given about when to use this tool versus alternatives such as termix_files_create_file, termix_hosts_create_ssh_host, or other folder-related tools. There are no conditions, exclusions, or mention of prerequisites like an active SSH session.

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