Quarantine Read Tool

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

With no annotations, the description carries the full behavioral burden. It discloses the two-layer quarantine extraction, the possible blocklist_warning, the prompt-injection risk, and explicitly instructs treating content as untrusted. It does not cover authentication or error behavior, but the output schema exists to fill return-value details.

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 compact and front-loaded with the core purpose, followed by a constraint and a security warning. The warning is somewhat long but necessary for safe usage; no sentence is wasted.

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 tool has a small parameter set, an output schema, and a security-critical warning. The description covers the file-type restriction and prompt-injection handling. It does not explain the quarantine layers or alternative tool selection, but an agent has enough to invoke the tool correctly with path and optional prompt.

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 100%, so the schema already documents both path and prompt. The description adds only the hint that Q-Agent extraction is involved, which loosely relates to the prompt parameter, but it does not meaningfully extend parameter semantics beyond the schema. 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?

The description states a specific action and resource: 'Read local file' with 'Text files only.' It adds scope with 'full quarantine: Layer 1 + Layer 2 Q-Agent extraction.' However, it does not explicitly distinguish itself from siblings like safe_read_tool or quarantine_content_tool, so differentiation is implicit rather than explicit.

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 makes clear that this is for reading text files locally under quarantine. It gives a clear constraint ('Text files only') but provides no when-to-use versus alternatives such as safe_read_tool, nor does it state when not to use this tool.

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