Delete Variables

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

The description goes far beyond the destructiveHint annotation by disclosing a full-document consumer check before any removal, refusal with VARIABLE_IN_USE including details.variablesInUse, and refusal with DOCUMENT_SCAN_INCOMPLETE when pages cannot be loaded. This gives the agent concrete knowledge of failure modes and safety behavior.

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 with no filler. The first sentence states the action and scope; the second explains the preflight check and error behavior. It is front-loaded and every sentence earns its place.

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 tool, the description covers the operation, the consumer-check precondition, and the possible error conditions in detail. Combined with the output schema and annotations, this is complete enough for an agent to select and invoke it safely.

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?

The schema already documents 100% of parameters, including mutual exclusivity between variableIds and collectionId, as well as the required verification names. The description only refers to 'specific variables or an entire collection,' which adds no new parameter-level 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?

The description begins with 'Delete specific variables or an entire collection,' naming the verb and resource clearly. It is a specific delete operation, but it doesn't explicitly distinguish itself from sibling tools like variable_manage or style_delete, so it lacks explicit sibling differentiation.

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 intended usage is implied by the title and delete semantics, and the description explains when the tool will succeed or fail. However, it does not explicitly state when to use this tool versus alternatives, nor does it name any sibling tool for contrast.

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