spss_normality_outliers

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

No annotations are provided, so the description carries the burden. It states it runs EXAMINE and checks normality/outliers, but does not disclose whether the operation is read-only, how missing data is handled, or potential failure modes. Some behavior is conveyed but not comprehensive.

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, front-loaded with the core purpose, and includes a necessary prerequisite. There is no redundancy or wasted words.

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 relatively simple analysis tool, the description provides sufficient context to select and invoke it. An output schema exists, so return values need not be described. Minor gaps include lack of annotation-level safety info and minimal param details, but overall acceptable.

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 coverage is 0%, so the description must compensate. It clarifies that variables are numeric and plots are optional, covering two of three parameters. However, file_path is not described, leaving some ambiguity about expected path format or supported file types.

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 specifically states 'Run SPSS EXAMINE to check normality and outliers for numeric variables', using a clear verb and resource. It also mentions optional diagnostic plots, making it distinct from sibling tools like descriptives or frequencies.

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 use for normality/outlier checks and provides a prerequisite (IBM SPSS Statistics installed), but it does not explicitly say when to use this tool versus alternatives like spss_descriptives or spss_chart_qqplot.

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