compress

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('compress into a ZIP file') but lacks critical details: whether it overwrites existing files by default, requires specific permissions, handles errors, or has performance/rate limits. For a mutation tool with zero annotation coverage, this is a significant gap.

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 zero waste. It's front-loaded with the core action and specifies key details (local scope, ZIP format). Every word contributes to understanding the tool's purpose without redundancy.

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?

Given the tool's complexity (3 parameters with nested objects, no annotations, no output schema), the description is inadequate. It covers the basic purpose but misses behavioral traits, parameter details, error handling, and output format. For a file mutation tool, this leaves the agent under-informed about critical usage aspects.

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%, so the description must compensate. It implies 'input' parameters (files/directories) and 'output' (ZIP file path), adding basic meaning. However, it doesn't explain the 'options' object or its sub-parameters (like 'level', 'password', 'overwrite'), leaving 3 parameters partially undocumented. The description adds some value but doesn't fully address the coverage gap.

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 clearly states the tool's purpose with a specific verb ('compress') and resource ('local files or directories'), and specifies the output format ('ZIP file'). It distinguishes from sibling 'decompress' by indicating the opposite operation, though it doesn't explicitly differentiate from 'getZipInfo' which inspects rather than creates ZIPs.

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 provides no guidance on when to use this tool versus alternatives like 'decompress' or 'getZipInfo'. It mentions the basic function but offers no context about appropriate scenarios, prerequisites, or exclusions. The agent must infer usage from tool names alone.

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