clearActiveCommentCollection

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

No annotations are provided, so the description carries full burden. It states the tool clears the active comment collection, implying a mutation (destructive operation), but doesn't disclose behavioral details like whether this requires specific permissions, is reversible, affects existing data, or has side effects. 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 directly explains the tool's effect. It's front-loaded with the core action and outcome, with no unnecessary words or redundant information. Every part of the sentence contributes to understanding the tool's purpose.

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 has no parameters, no output schema, and no annotations, the description adequately explains what the tool does. However, as a mutation tool, it lacks details on behavioral aspects like permissions, reversibility, or error conditions. The description is complete for a simple operation but could benefit from more context about its impact.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it doesn't contradict the schema. Baseline is 4 for zero parameters, as the description appropriately focuses on purpose rather than inputs.

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 action ('Clear') and the target ('active comment collection'), explaining that it makes comment search fan out across all collections. It distinguishes from sibling 'clearActiveCollection' by specifying 'comment collection' versus general collection, but doesn't explicitly contrast with other comment-related tools like 'listCommentCollections' or 'removeCommentCollection'.

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 when you want to broaden comment search from a specific collection to all collections, but doesn't explicitly state when to use this tool versus alternatives like 'setActiveCommentCollection' or 'removeCommentCollection'. It provides context but lacks explicit guidance on prerequisites or exclusions.

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