quarantine_search_tool

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

With no annotations, the description fully covers behavior: pipeline stages (L0 to L3), return format (synthesized prose, source URLs, structured extraction with summaries and relevance scores), and a specific warning about classifier_warning indicating potential compromised content. This adds significant transparency.

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?

Description is concise (7 lines) and well-structured: purpose sentence, pipeline overview, output description, and warning. No extraneous information.

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?

Given complexity (multi-stage pipeline) and presence of output schema, the description covers key aspects: pipeline flow, output format, and a critical warning. However, it does not explain the individual L stages or how this relates to siblings, which could be useful.

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 baseline is 3. The description does not add new parameter semantics beyond what the schema already provides (e.g., query, prompt, num_results are already documented in schema). No additional detail is given.

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 'Search the web with full quarantine pipeline' and explains pipeline stages, making the purpose specific. However, it does not explicitly differentiate from sibling safe_search_tool, which likely also performs search.

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 vs alternatives like safe_search_tool. The description implies it's for searches needing quarantine, but no when-not or exclusion criteria are provided.

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