Delete Variables

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

Annotations already indicate destructiveHint and idempotentHint. The description adds valuable behavioral detail: a full-document consumer check before deletion and rejection if any target is in use. This goes beyond what annotations provide.

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?

Two sentences with no unnecessary words. First sentence states purpose, second adds a critical behavioral condition. Extremely concise and well-structured.

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's complexity (destructive with consumer check, two mutually exclusive params, has output schema), the description covers key behavioral context. Minor omission: no mention of success outcome, but output schema likely covers return structure.

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 description coverage is 100% and already explains mutual exclusivity between variableIds and collectionId. The description reiterates the purpose but does not add new semantic meaning beyond what the schema provides.

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?

Clearly states it deletes specific variables or an entire collection. The verb 'delete' and resource 'variables' or 'collection' are explicit, and it distinguishes from sibling tools like variable_list or variable_manage which do not perform deletion.

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?

Implies usage through parameter descriptions (mutual exclusivity) and mentions a consumer check, but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. No mention of alternatives like variable_manage for partial updates.

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