unzip_path

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

Annotations already indicate this is not read-only, and the description adds little beyond restating that extraction happens. It does not disclose whether existing files in the destination are overwritten, whether the destination must already exist, or what side effects occur during extraction.

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 direct sentence with no filler or repeated boilerplate. It is appropriately sized for a two-parameter tool, though it could have included a bit more operational detail without becoming bloated.

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?

With no output schema, the description does not explain what the agent should expect after invocation, such as success signals or error conditions. It also omits behavioral details like overwrite policy and destination creation, leaving meaningful gaps for a mutating filesystem operation.

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 carry the semantic load. It usefully maps path to 'a zip archive' and destination to 'a destination directory', but it does not clarify path formats, whether the destination is created, or how conflicts are handled.

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 uses a specific verb ('Extract') and resource ('a zip archive') with a destination directory, making the operation unmistakable. It also distinguishes itself from the sibling tool zip_paths, which performs the opposite operation.

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 explicit when-to-use guidance and does not mention alternatives or exclusions. The intended use case is only implied by the verb 'Extract', leaving an agent without routing guidance relative to sibling file tools.

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