guardian_quarantine

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

Since no annotations are provided, the description carries the full burden. It discloses the destructive nature of isolate and release, explains the file relocation process, and notes that all actions are logged. This provides adequate behavioral context, though error handling or missing parameter behavior is not mentioned.

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 two sentences with no fluff. The first sentence introduces the three actions, and the second provides critical behavioral details. Highly efficient and front-loaded.

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 three actions and no output schema, the description explains the core behavior of each action and the logging mechanism. It lacks explicit mention of return values or error conditions, but given the tool's straightforward nature, the description is mostly 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?

Schema description coverage is 67% (2 of 3 parameters have descriptions). The description adds context about the isolate and release actions mapping to file_path and file_hash respectively, but does not significantly elaborate on parameter semantics beyond the schema. Baseline 3 is appropriate given moderate coverage and some added value.

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 three actions (isolate, release, list) and the resource (quarantined files), making the purpose unambiguous. It distinguishes from sibling tools like guardian_scan by focusing specifically on quarantine operations.

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 explicitly notes that isolate and release are destructive and explains the mechanics (copy to ~/.guardian/quarantine/, remove original, reverse). This provides context for when to use each action, though it doesn't explicitly state when not to use or mention alternatives.

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