Compress files

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, but the description adds no behavioral context beyond the basic action. It does not disclose whether existing archives are overwritten, whether compression happens in place, what formats are supported, or whether a session is required. The description does not contradict annotations, but it also does not enrich them.

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 and front-loaded, but it wastes its second sentence by repeating the first ('Compress files. Compresses files and/or directories...'). It is concise but not information-dense.

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 tool with four undocumented parameters, no output schema, and no usage guidance, the description is incomplete. It does not mention supported archive formats, required session context, or what the tool returns. The sibling list shows related file tools, but the description does not connect to them.

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 four parameters (paths, format, sessionId, archiveName). The agent must guess what 'format' values are valid, what 'paths' expects, and how 'archiveName' is used. The description provides no compensation for the schema's lack of documentation.

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 verb and resource ('Compress files... on the remote host'), but it is largely redundant with the title and does not distinguish this tool from its sibling termix_files_extract_archive_file or other file operations. It identifies the action but not the specific scope or output.

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 on when to use this tool versus alternatives like extract_archive_file, copy_file_directory, or move_file_directory. The description only says it compresses files/directories, leaving the agent to infer the appropriate context.

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