delete_variable_collection

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

Beyond the destructiveHint annotation, the description discloses the full destructive scope (removes collection, all variables and modes) and the side effect that bindings revert to raw values. It also specifies the return shape, enriching the tool's behavioral context.

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 three sentences with no fluff. It front-loads the action and consequences, then gives the alternative, then the return value—every sentence 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?

The description is self-contained, covering purpose, destructive impact, side effects, alternative usage, and return value. Given its cascading deletion behavior and lack of an output schema, this level of detail makes it fully sufficient for an agent.

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 sole parameter collectionId is already fully described in the schema (100% coverage). The description only repeats 'by id' without adding extra format, source, or prerequisite details, so it meets the baseline but does not exceed it.

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 the specific verb 'Delete' and identifies the resource (variable collection), while explicitly contrasting with delete_variable for single variables. This clearly distinguishes it from sibling tools and states the operation's scope.

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?

It explicitly states 'To delete a single variable instead, use delete_variable,' providing a clear alternative and when-not-to-use guidance. This helps the agent choose between delete_variable_collection and delete_variable.

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