Read ZIP Context Safely

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

With annotations already indicating read-only and idempotent behavior, the description adds valuable context: operates entirely in memory, does not extract to disk, applies filtering categories, and returns a virtual file tree and text contents. No contradictions with annotations.

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, information-dense sentence that front-loads the main verb and object, then packs in filters, return type, and safety behavior without redundancy or waste.

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?

The description covers the core purpose, return type, and safety aspects, and annotations cover the read-only profile. However, it omits explanations for the optional parameters and does not address edge cases (e.g., password-protected zips, empty archives). Given low schema coverage, these are notable gaps.

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 only 33% (only 'path' has a description). The description does not compensate for undocumented 'max_files' and 'max_output_bytes'—it doesn't mention them or explain their function. The filtering categories listed are internal behaviors, not parameter meanings, leaving the agent without guidance.

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: 'Inspect a .zip archive entirely in memory' with specific filtering and return behavior. It distinguishes itself from sibling tools (read_code_context, analyze_images) by focusing on ZIP archives and in-memory processing.

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 context implies this tool is for reading ZIP archives, but the description does not explicitly mention when to use it versus alternatives or state exclusions. It lacks guidance like 'for code files use read_code_context' or 'not for large archives beyond limits'.

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