delete_variable_mode

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

With no annotations, the description carries the full behavioral burden and discloses little. It signals a destructive 'Remove' and mentions the confirmDelete guard, but says nothing about reversibility, whether deletion fails when the mode is in use, or what happens to variables bound to the mode.

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, front-loaded with the action and scope, followed immediately by the required precondition. No filler.

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?

A destructive tool with no annotations, no output schema, and 0% schema description coverage needs more: failure modes, reversible-or-not, and side effects on bound variables are all absent. What exists is minimally viable at best.

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 should compensate. It adds genuine meaning for confirmDelete (must be true) beyond the bare boolean in the schema, and collectionId/modeId are implied by the scope phrase, but the identifier parameters remain unelaborated (format, source).

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?

States a specific verb and resource ('Remove a mode from a variable collection'), which cleanly separates it from delete_variable and delete_variable_collection. It does not explicitly name those siblings, but the collection-scoped wording makes the target unambiguous.

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 or routing versus related siblings like set_variable_mode, rename_variable_mode, or delete_variable. The confirmDelete precondition is operational, not usage context, so an agent gets no help deciding when this deletion is the right call.

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