zip_create

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

No annotations are provided, so the description carries the transparency burden. It discloses the underlying implementation (PowerShell Compress-Archive), wildcard support, and the .zip extension requirement. However, it omits critical behaviors like what happens if the destination exists (overwrite?), error handling, or whether folder structure is preserved. The disclosed details help but are incomplete.

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 concise: two sentences that front-load the main action and follow with usage context. It includes only essential information without fluff, making it easy to scan.

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 simple two-parameter tool with no output schema, the description covers the main purpose and usage. However, it does not explain important edge cases like overwrite behavior, directory recursion, or potential side effects. Given the lack of annotations, the description should provide a bit more context to be fully complete.

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?

The input schema has 100% coverage with descriptions and examples for both source and destination. The description adds a note about wildcards and the .zip extension, but these are already mentioned in the schema examples. The description does not add significant extra meaning beyond the schema.

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 function with a specific verb+resource: 'Create a ZIP archive from files or folders.' It distinguishes from sibling tools like zip_extract by focusing on compression/creation rather than extraction. The use cases (backup, sharing, archiving) reinforce the purpose.

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?

It explicitly says 'Use this tool to compress files/folders into a .zip file for backup, sharing, or archiving', providing clear context for when to use it. It does not explicitly mention when not to use it or name alternatives, but the distinction from zip_extract is obvious. Wildcard and destination extension guidance are also given.

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