altair_clean_data

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

No annotations are provided, so the description must disclose behavioral traits. It describes what operations are performed (replace missing values, remove duplicates, drop columns) but fails to mention important behaviors such as whether the tool modifies the file in-place or returns a new dataset, required authentication, or limitations on data size.

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 long: the first sentence states the core purpose, and the second provides context via action numbers. It is front-loaded, concise, and contains no redundant information.

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?

With no output schema, the description should clarify what the tool returns or whether it has side effects. It only states 'clean a dataset' without explaining the output format or any changes to the input file. Given the 5 parameters and lack of annotations, the description leaves significant gaps.

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?

All parameters are fully described in the schema (100% coverage). The description reiterates the operations but does not add significant meaning beyond the schema, such as default behavior or typical usage patterns. Baseline score of 3 is appropriate.

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 tool's purpose: cleaning a dataset with specific operations (missing value handling, duplicate removal, column dropping). It also references actions 11-15 and 20 of data preparation, providing context. While it doesn't explicitly differentiate from sibling tools, the operations are distinct enough for an agent to understand the tool's scope.

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 implies usage for cleaning tasks but does not explicitly state when to use this tool versus alternatives like altair_normalize_data or altair_split_data. The reference to specific data preparation actions gives some guidance, but no exclusions or comparison are provided.

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