unmount_image

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

No annotations are provided, so the description is the sole source of behavioral information. The term 'cleanly' hints at safe and proper unmounting, but it does not disclose potential side effects (e.g., behavior if the image is still in use, whether it is idempotent, or error conditions). This leaves some ambiguity for a destructive operation.

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 sentence that conveys the essential purpose without any extraneous words. It is front-loaded with the action and resource, and every word serves a purpose. Perfect conciseness.

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 tool with no parameters and no output schema, the description provides sufficient context: it tells what the tool does and when to use it ('after analysis'). It could mention that it is the counterpart to mount_image or specify behavior if called multiple times, but the current description is largely adequate for a simple 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?

The tool has zero parameters, so the input schema is trivially complete. With schema coverage at 100%, the description does not need to add parameter details. The baseline for zero parameters is 4, and the description meets that without requiring additional semantic explanation.

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 specifies the action 'Unmount' and the resource 'forensic image', with additional context 'cleanly after analysis'. The tool name and description together uniquely identify its purpose, distinguishing it from sibling tools like mount_image.

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 phrase 'after analysis' provides a clear timing guideline for when to use this tool. While it does not explicitly exclude use before mounting or list alternatives, the sibling tool mount_image serves as the counterpart, making the usage context evident.

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