File Compress

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

With no annotations, the description carries the full behavioral burden; it does flag that this is a write operation (写操作), which is genuinely useful context. However, it omits anything about overwrite behavior for an existing output_path, permission requirements, or the effect of the password/level options, all of which matter for a mutation tool.

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?

A single short sentence with zero padding and no redundancy. It is efficient, though its brevity borders on under-specification rather than deliberate conciseness.

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?

This is an 8-parameter write tool with no annotations, so the description should carry more behavioral context. It says nothing about archive format expectations, overwrite risk, encryption semantics, or error conditions, leaving significant gaps despite the output schema covering return values.

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 100%, so all 8 parameters (host, port, level, scheme, profile, password, output_path, source_paths) are already documented in the schema. The description adds no further parameter meaning, making the baseline 3 appropriate.

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 (compress) and resource (files/directories into an archive), so the action is unambiguous. It does not explicitly differentiate itself from the inverse sibling file_extract, but the meaning is clear from the verb alone.

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 when-to-use context, no prerequisites, and no reference to alternatives such as file_extract for the reverse operation. The agent gets no guidance on when this is the right tool versus other file operations.

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