ecp_files_compress

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

With no annotations, the description bears the full burden of behavioral disclosure, but it only states the action. It does not reveal important behavior such as the archive format (zip/tar/gz), what current_directory is used for, whether existing output files are overwritten, or how paths are resolved. The description confirms the tool creates an archive but leaves significant side effects and constraints undisclosed.

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 efficient sentence with no filler words. It front-loads the action and resource, which is appropriate for a straightforward tool. It is concise, though arguably too sparse, which is a completeness issue rather than a structure issue.

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 that creates an archive, has no annotations, no output schema, and 0% schema coverage, the description is under-specified. It omits archive format, path resolution semantics, overwrite behavior, return values, and the role of current_directory. An agent would not have enough information to safely invoke this tool with confidence.

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 coverage is 0%, so the description must compensate for parameter meaning. 'Files/folders' loosely maps to file_paths and 'archive' maps to output_filename, giving some hint, but current_directory is entirely unexplained. The description does not clarify whether paths are relative to current_directory, whether it must be absolute, or how the parameters relate to each other.

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 specific verb ('Compress') and resource ('files/folders into an archive'), making the tool's core purpose clear. It does not explicitly distinguish this from the sibling ecp_files_extract, but the action is unambiguous enough that an agent can tell it is the compression counterpart.

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?

The description gives no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. While it implies 'use when you need to create an archive,' it does not mention the sibling extract tool or any conditions that would make compression inappropriate.

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