target_encode

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

With no annotations, the description carries the full burden of behavioral disclosure. It accurately describes the transformation (smoothed mean replacement), introduces the smoothing parameter, and warns about the data leakage pitfall. It does not explicitly state whether the operation mutates the dataframe in place or returns a new one, but the phrase 'Each category is replaced' implies in-place modification.

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 plus an example, all of which are informative and directly relevant. It does not waste words and the example provides a clear, concrete usage pattern. 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?

The description covers the tool's purpose, usage conditions, a critical warning, and includes a concrete example. With an output schema present, return values need not be explained. The only notable gap is the undocumented df_name parameter, but overall the description is well-rounded for a tool of this complexity.

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. It mentions the columns, target_column, and smoothing parameters in the example and text, but does not describe df_name at all. The meaning of smoothing is only partially explained as 'smoothed mean' without detailing how the numeric value affects the encoding, leaving ambiguity about its exact role.

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 a specific action ('Target-encode high-cardinality categorical columns') and explains the mechanism ('Each category is replaced by the smoothed mean of the target variable'), distinguishing it from sibling encoding tools like one_hot_encode, label_encode, and frequency_encode. The mention of 'high-cardinality' and 'smoothed mean' makes the purpose unmistakable.

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 clear usage context: 'Good for columns with many unique values. Best for high-cardinality (>10 categories).' It also gives a critical procedural guideline about data leakage: 'split data first with train_test_split, then encode training set only.' However, it does not explicitly mention when not to use the tool or name alternative encoding methods, so it falls short of a 5.

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