delete_variable

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

The description only states 'delete', implying a destructive action, but does not disclose any behavioral traits such as irreversibility, side effects (e.g., if variable is referenced elsewhere), or authorization requirements. With no annotations provided, the description fails to convey what the agent should expect beyond the basic operation.

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 extremely concise at 5 words: 'Delete a variable by ID'. This is appropriate for a simple delete tool; every word is necessary. However, it could be slightly more informative without losing conciseness.

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 one-parameter delete tool with no output schema, the description is minimally adequate. It covers the essential action and target identifier. However, it lacks completeness in terms of error scenarios (e.g., what if ID doesn't exist) and any behavioral context beyond the basic operation.

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 description mentions 'by ID' but does not explain what the ID represents or how to obtain it. The input schema has a single required string parameter 'id' with 0% schema description coverage, meaning the agent gets no additional context about the parameter's format, constraints, or semantics from the description.

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 action 'Delete' and the resource 'variable by ID'. It is specific and distinguishes from sibling tools like create_variable or update_variable. However, it does not provide any additional context about what a variable is, but for a delete operation, the purpose is adequately clear.

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 description does not provide any guidance on when to use this tool versus alternatives. While it's obvious for a delete, there is no mention of prerequisites, safety checks, or when not to use it (e.g., if the variable is in use). This leaves room for misuse.

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