Delete Variables

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

Beyond the annotations (destructiveHint, idempotentHint, openWorldHint), the description adds a crucial behavioral trait: 'Runs a full-document consumer check first and rejects the whole operation if any target is still in use.' This provides significant transparency not captured by annotations alone.

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 two sentences long, front-loaded with the action, and every sentence adds essential information. No redundancy or unnecessary details.

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 presence of an output schema (not shown) and full parameter schema coverage, the description covers the key behavioral aspect (consumer check) and the two delete modes. A minor gap is the lack of explicit success outcome, but the output schema likely covers that.

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?

Schema coverage is 100%, so the description adds little beyond mapping 'specific variables' to variableIds and 'collection' to collectionId. It does not explain the safety verification parameters (variableNames, collectionName), but the schema already describes them.

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 'Delete specific variables or an entire collection,' providing a specific verb and resource. It distinguishes from sibling tools like variable_list and variable_manage by the explicit deletion action and the consumer check detail.

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 (when deleting variables) but lacks explicit guidance on when not to use or alternatives. The consumer check and rejection on usage are mentioned, but no direct comparison to siblings or exclusion criteria.

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