repl_delete_variable

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds that it returns confirmation with remaining variables, which is useful context beyond annotations. However, it does not disclose other behaviors such as error handling or side effects beyond the annotation coverage.

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 only two sentences long, front-loads the action, and includes the return value. Every sentence adds value with no redundancy or 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?

The tool is simple, and the annotations (destructiveHint, idempotentHint) plus the output schema cover much of the behavioral context. The description adequately states the result (confirmation with remaining variables). It lacks only parameter details, but the schema provides the required arguments. The description is complete enough for selecting and invoking the tool.

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 does not mention the parameters session_id or var_name, and the schema description coverage is 0%. The schema provides minimal descriptions ('Variable name.' and 'Session ID.'), but the tool description adds no additional semantic meaning. Since coverage is low, the description was expected to compensate but did not.

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 uses the specific verb 'Delete' with a clear resource ('a specific variable from a session's namespace'). This clearly distinguishes it from sibling tools like repl_get_variable, repl_set_variable, and repl_clear_namespace.

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. It does not mention, for example, that repl_clear_namespace should be used to delete all variables, or any other usage context. The purpose is implied but not explicit.

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