removeCommentCollection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions deletion but doesn't specify if this action is reversible, requires specific permissions, or has side effects like affecting related data. This leaves critical behavioral traits unclear for a destructive operation.

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 states the tool's function without unnecessary words. It is front-loaded with the key action and resource, making it easy to parse quickly.

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 destructive tool with no annotations, no output schema, and minimal parameter guidance, the description is insufficient. It doesn't cover important aspects like confirmation prompts, error handling, or what happens to associated data, leaving gaps in understanding the tool's full 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?

The input schema has 0% description coverage, but the description doesn't add any semantic details about the 'collectionId' parameter, such as format or source. Since there's only one parameter, the baseline is 4, but the lack of any parameter-specific guidance reduces the score to 3.

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 ('Delete') and the resource ('a local comment collection and its search index'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'removeCollection' or 'clearActiveCommentCollection', which might handle similar resources differently.

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 guidance is provided on when to use this tool versus alternatives like 'removeCollection' or 'clearActiveCommentCollection'. The description lacks context about prerequisites, such as whether the collection must be inactive or if data loss is permanent, leaving the agent to infer usage scenarios.

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