handle_missing_values

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

The description explicitly states 'Reversible,' which is a meaningful behavioral disclosure beyond the schema. However, with no annotations provided, it does not mention side effects on the session, what happens when 'drop' is used, whether original data is modified, or whether constant imputation requires a user-supplied value. The behavior is only partially disclosed.

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, containing only two short sentences with no redundant or filler content. The main purpose is front-loaded, and the reversibility note is a separate, valuable behavioral detail.

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 mutation-like operation with four parameters and no annotations, the description is too minimal to be fully actionable. An agent would not know that 'constant' likely requires a non-null value, how the operation interacts with session state, or when to prefer it over find_missing_values or undo_last_operation. The output schema helps, but the usage context remains incomplete.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It names the strategies and the column, but it does not explain the 'value' parameter, which is essential for the 'constant' strategy, nor does it clarify the role of session_id. The description largely repeats the strategy enum already present in the schema.

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 identifies the operation as handling missing values in a column and enumerates five concrete strategies: mean, median, mode, constant, and drop. This is specific enough to distinguish it from the sibling tool find_missing_values, which presumably only detects missing values, though it does not name that distinction explicitly.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as having an active session or having previously used find_missing_values. The intended use is only implicit from the tool name and the generic phrase 'Handle missing values'.

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