annotation.undefine_data_var

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

No annotations are present, and the description does not disclose any behavioral traits. It does not state whether the operation is destructive, reversible, requires specific permissions, or affects other data. The agent cannot assess the impact of invoking this tool.

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 short (three words), but this is under-specification rather than concise effectiveness. No sentence earns its place because the description provides virtually no actionable information. It is not appropriately sized for a tool with two parameters and many siblings.

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?

Given the lack of annotations, missing output schema, zero parameter documentation, and the presence of many sibling tools, the description is completely inadequate. It does not explain the tool's purpose, parameters, return value, or relationship to other annotation tools, leaving the agent with no useful context.

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 input schema has 0% description coverage, and the description does not mention either parameter ('session_id' or 'address'). It fails to explain what 'address' represents (e.g., a memory address, a variable name) or the role of 'session_id', leaving the agent to guess parameter semantics.

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 'Undefine data variable' is a tautology that restates the tool name without explaining what 'undefine' means in this context. It does not differentiate from closely related siblings like 'annotation.undefine_symbol' or 'annotation.define_data_var', leaving the agent unsure of what this tool actually accomplishes.

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 guidance is provided on when to use this tool versus alternatives. For example, there is no explanation of when to use 'annotation.undefine_data_var' instead of 'annotation.undefine_symbol' or 'annotation.rename_data_var'. The description offers no context for decision-making.

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