spss_normality_outliers

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

With no annotations, the description carries the burden of behavioral disclosure. It transparently states that the tool invokes SPSS EXAMINE and requires IBM SPSS Statistics to be installed, and it notes that plots are optional. It does not explicitly state whether the operation modifies data or is read-only, though the verb 'check' suggests an analytical rather than mutating action.

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?

Two sentences convey the procedure, purpose, variable scope, optional behavior, and a critical prerequisite. There is no filler, and the most important information is front-loaded.

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 main purpose, the underlying SPSS command, the prerequisite installation, and the optional plots. However, it lacks explicit guidance on file_path semantics and on how to choose this tool over closely related sibling statistical procedures, even though the modest parameter complexity and existing output schema reduce the overall gap.

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 schema has 0% description coverage, so the description must compensate. It clarifies that variables should be numeric and that plots are diagnostic, but it leaves the required file_path parameter as just a string with no indication of the expected file format or SPSS dataset context. The variables array item type is also unspecified in both schema and description.

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 verb and resource: it runs SPSS EXAMINE to check normality and outliers for numeric variables. It also mentions optional diagnostic plots, which distinguishes it from the many sibling statistical and data-management tools.

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 the appropriate use case: checking normality and outliers for numeric variables. It does not explicitly contrast this with sibling tools such as spss_descriptives or spss_graph_boxplot, nor does it state when not to use it, though the SPSS prerequisite is mentioned.

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