delete_variable

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the confirmation guard ('Requires confirmDelete=true'), which signals this is guarded and intentional, but never states the deletion is permanent/irreversible, whether dependent bindings are affected, or what authorization is needed.

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 short sentences with the action and the safety requirement front-loaded; nothing is wasted. It is arguably tighter than needed for a destructive tool, but structurally efficient.

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, annotation-free tool with no output schema and undocumented parameters, the description should at minimum state permanence and consequences. It conveys identity and the confirm flag but leaves irreversibility, side effects, and error behavior unaddressed.

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 0%, so the description must compensate. It clarifies that variableId identifies the target and that confirmDelete must be true (not merely present), adding real semantic value for the boolean, but it adds nothing about the expected id format or failure modes for either parameter.

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?

Clear verb+resource ('Delete an existing variable') with the identifier named, which separates it from delete_variable_mode and delete_variable_collection by resource noun. It does not explicitly contrast itself against those siblings or note that it operates on a single variable rather than a collection, so it stops short of a 5.

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 when-to-use guidance, no prerequisites (e.g. variable must exist, collection must be editable), and no routing to alternatives such as delete_variable_mode or delete_variable_collection. Usage is only implicitly inferable from the verb.

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