clearActiveCollection

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

With no annotations provided, the description carries the full burden. It adds valuable behavioral context via '[~instant]' (performance characteristic) and explains the search scope expansion effect. However, it omits safety details (whether this deletes data vs. just deselecting) and doesn't clarify if this affects search types beyond transcripts.

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 efficient sentence with a brief performance annotation. It is front-loaded with the action ('Clear the active collection') and contains no redundant or wasted words.

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 simple state-reset tool with no parameters and no output schema, the description is reasonably complete. It explains the functional effect on the primary use case (transcript search). A minor gap is the lack of explicit clarification that this operation doesn't destroy the collection data (distinguishing it from removeCollection), but the naming convention makes this reasonably clear.

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 input schema has zero parameters, establishing a baseline score of 4. The description appropriately doesn't invent parameters, and the empty schema with additionalProperties: false is self-documenting.

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 specific action ('Clear the active collection') and its functional consequence ('so transcript search fans back out across all collections'). It effectively distinguishes this from siblings like setActiveCollection (inverse operation) and clearActiveCommentCollection (mentions 'transcript' specifically vs. comments).

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 usage context through the explanation of the fan-out effect, suggesting when you'd want to use this (to broaden search scope). However, it lacks explicit 'when to use' guidance or direct comparison to setActiveCollection as the alternative for filtering.

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