clearActiveCommentCollection

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

With no annotations provided, the description carries the full disclosure burden. It successfully explains the behavioral consequence (search scope changes to span all collections) and includes performance characteristics ('[~instant]'), indicating synchronous/fast execution. It implies this is a state reset rather than deletion (distinguishing from removeCommentCollection).

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?

Single efficient sentence with zero waste. The action is front-loaded ('Clear the active comment collection'), followed by purpose clause ('so...'), and performance tag ('[~instant]'). Every element 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 zero-parameter state management tool without output schema, the description adequately covers the essential context: what it does, the immediate effect on system behavior (search scope), and performance characteristics. It could be improved by explicitly naming affected operations like searchComments or readComments, but 'comment search' provides sufficient context.

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?

Baseline score of 4 applies as there are zero parameters. The description does not need to compensate for parameter documentation since the input schema is trivial (empty object with additionalProperties: false).

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 uses a specific verb ('Clear') and identifies the exact resource ('active comment collection'). It distinguishes from the sibling tool 'clearActiveCollection' by specifying this is for comments, and explains the functional effect on search scope ('fans back out across all comment collections'), clearly differentiating it from 'setActiveCommentCollection'.

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?

Usage is implied through the explanation of effect ('so comment search fans back out...'), suggesting when to use it (when you want global search scope). However, it lacks explicit guidance like 'Use this when you want to search across all collections instead of a specific one' or naming the alternative 'setActiveCommentCollection' for comparison.

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