delete_variables

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

Discloses full-document consumer check, rejection if in use, and scope limitation. Since no annotations are provided, the description fully bears this burden and does so well.

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 concise sentences, front-loaded with action and parameters, no wasted words.

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?

Adequate for a delete action; explains pre-check behavior. No output schema, but description covers key points. Could mention success behavior implicitly.

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 has 100% coverage, but description adds mutual exclusivity context and consumer check behavior, which goes beyond mere parameter descriptions.

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 tool deletes specific variables by ID or an entire collection, with mutual exclusivity. It is distinct from siblings like 'manage_variables' and 'set_bound_variable'.

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?

Explains when to use variableIds vs collectionId and mutual exclusivity. Mentions consumer check and document limitation, but could be more explicit about prerequisites like ensuring variables are unused.

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