spss_repeated_measures_anova

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

With no annotations, the description must carry behavioral disclosure. It usefully states that IBM SPSS Statistics must be installed, an important external dependency, and 'Run' implies an analysis rather than a data mutation. However, it does not describe error behavior, variable type constraints, or what the returned output represents.

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, each earning its place: the first identifies the operation and the required input pattern, and the second gives the prerequisite. The essential information is front-loaded and there is no filler.

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 complex statistical tool with no annotations and 0% schema description coverage, the description covers the core invocation (factor, levels, variables) but omits behavior around include_pairwise and any assumptions about the data/variables. An output schema exists, but the description alone is only minimally complete.

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 this description compensates for the key required parameters by saying to provide the within-factor name, number of levels, and one variable per level. file_path is self-evident, but the optional include_pairwise parameter is not explained despite having a default value.

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 uses a specific verb ('Run') and names the exact analysis ('SPSS repeated-measures ANOVA'), clarifying it is the within-subject GLM. This distinguishes it from sibling tools such as spss_anova or spss_manova.

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 phrase 'repeated-measures ANOVA (within-subject GLM)' gives a clear statistical context for when the tool applies. It does not name alternatives or state when not to use it, but the repeated-measures framing and 'Requires IBM SPSS Statistics' prerequisite provide enough contextual guidance.

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