spss_flip

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

There are no annotations, so the description carries the full burden. It mentions two parameters but does not disclose whether the original file is modified, how output_path is handled, or whether the operation is reversible. The 'Requires IBM SPSS Statistics' note describes the environment, not the behavior of the operation.

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 compact and front-loads the core purpose. It packs the two important parameter explanations into one sentence without waste, though it is somewhat terse and would benefit from a clearer parameter list.

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?

Given the large sibling family of transform tools and the presence of an output schema, the description still misses essential context: it doesn't say whether the transform writes to output_path or mutates the source file, and it fails to differentiate from spss_cases_to_vars/spss_vars_to_cases. An agent lacks enough information to invoke it correctly and safely.

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 property descriptions are entirely absent (coverage 0%), so the description must compensate. It usefully explains 'variables' (subset to flip, default all) and 'newnames_variable' (values become column names), but it omits any semantics for the required file_path and for output_path, leaving those parameters under-specified.

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 states a precise transformation—'Transpose rows and columns'—and names it as the SPSS FLIP command. This clearly distinguishes it from sibling data-shaping tools like spss_cases_to_vars and spss_vars_to_cases.

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?

No guidance is given about when to choose FLIP over alternative reshaping tools. The only qualification is the environmental requirement 'Requires IBM SPSS Statistics,' which is a prerequisite, not a usage selector. An agent receives no instructions on when to use this vs siblings.

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