setActiveCollection

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

No annotations are provided, so the description carries the full burden. It states this is a 'Set' operation, implying it's a mutation that changes system state, but doesn't disclose behavioral traits like whether it requires specific permissions, if changes are persistent, what happens on error, or if it affects other operations. For a mutation tool with zero annotation coverage, this is a significant gap.

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 that front-loads the key information: what the tool does and its context. There is no wasted text, and it's appropriately sized for a simple tool with one parameter.

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 the tool's complexity (simple mutation with one parameter), no annotations, no output schema, and 0% schema coverage, the description is minimally adequate. It explains the purpose and parameter semantics but lacks behavioral details like error handling or system impact. For a mutation tool, more completeness would be beneficial.

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 description adds meaning beyond the input schema: it explains that 'collectionId' is used to set the default collection for transcript searches when omitted. The schema has 0% description coverage (no parameter descriptions), so the description compensates by clarifying the parameter's purpose. However, it doesn't specify the format or constraints of collectionId.

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 tool's purpose: 'Set the default collection that transcript search should focus on when collectionId is omitted.' It specifies the verb ('Set'), the resource ('default collection'), and the context ('transcript search'). However, it doesn't explicitly differentiate from its sibling 'setActiveCommentCollection', which appears to serve a similar purpose for comment collections.

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 this tool: when you want to set a default collection for transcript searches that omit collectionId. It provides some context but doesn't explicitly state when not to use it or mention alternatives like manually specifying collectionId in searches. No prerequisites or exclusions are mentioned.

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