Quarantine Search Tool

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It details the pipeline stages, the structured output, and importantly warns about classifier_warning indicating potentially compromised content. This goes well beyond a simple search tool description, though it does not mention permissions or explicitly state read-only behavior.

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 reasonably compact and front-loaded with the core action. The pipeline breakdown and the IMPORTANT warning each add valuable context without excessive verbosity. Slight redundancy exists between 'structured JSON output' and 'structured extraction,' but overall every sentence earns its place.

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 this complexity, the description covers the pipeline, output composition, and a critical edge case. The output schema exists and covers return format. It is complete enough for an agent to invoke the tool correctly, though it could be slightly stronger by explicitly stating when to prefer this tool over safe_search_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?

Schema coverage is 100%, so the input schema already documents query, prompt, and num_results. The description adds some context around the prompt being an 'extraction instruction for L3' and mentions structured output, but it does not materially extend the meaning of any individual parameter beyond the schema. A baseline of 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 clearly states the verb and resource: 'Search the web with full quarantine pipeline.' It also explains the pipeline stages and output format, which makes the tool's purpose concrete. However, it does not explicitly differentiate this tool from sibling safe_search_tool, relying on the 'full quarantine pipeline' phrase to imply the distinction.

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 implies when to use the tool (when a full quarantine pipeline and structured extraction are needed) but never explicitly states when not to use it or which sibling tool to choose instead. For example, it doesn't contrast with safe_search_tool or quarantine_content_tool. The usage context is inferable but not directly stated.

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