archive_slack

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

No annotations provided, so description carries full burden. It states the tool 'identifies and hex-dumps gaps' and explains slack spaces are unused bytes that conceal data without altering functionality. However, it does not disclose whether the operation is read-only, any required permissions, or potential side effects like file modification.

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?

Two sentences, no filler, highly efficient. Every sentence contributes to understanding the tool's purpose and behavior.

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?

No output schema, but description adequately covers what the tool does and its main behavioral aspect (hex-dumping slack spaces). Lacks details on return values or handling of edge cases, but overall sufficient for a simple analysis tool.

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?

Input schema covers both parameters with descriptions. Description adds no further meaning beyond schema: file_path is simply 'Path to ZIP archive' and max_dump_size is 'Max bytes to hex-dump per slack space (default: 256)'. Baseline 3 is appropriate.

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?

Description clearly states it performs 'Slack space analysis for ZIP archives' and explains what slack spaces are and their relevance to hiding data. It distinguishes from sibling tools like archive_structure and archive_comment by specifying a unique focus on gaps between local file entries.

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?

No explicit guidance on when to use this tool versus alternatives. Description implies usage when investigating hidden data in ZIP archives, but lacks when-not-to-use or exclusion criteria.

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