spss_select_if

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

With no annotations provided, the description carries the full burden. It discloses that the operation is permanent and that output_path can save the filtered result as a new .sav file, which is useful. However, it does not clarify the exact behavior when output_path is null—whether the original file is overwritten or modified in place.

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?

Three short, purposeful sentences. The core behavior is front-loaded, output_path usage is explained, and the SPSS dependency is stated without any redundant 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 three-parameter tool, the description covers the core behavior and the optional output parameter, and an output schema is present. Still, it lacks explicit detail about what happens without output_path, how file_path is used, and when to choose this over sibling tools.

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 the description must compensate. It explains the condition parameter as an SPSS SELECT IF condition and explains output_path as the destination for a new .sav file, but file_path is left to inference and not explicitly described.

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 action ('Permanently keep only cases matching a condition') and the SPSS command it corresponds to ('SELECT IF'), with a clear resource (cases in a data file). It is distinct enough in meaning but does not explicitly name any sibling tool it differs from, such as spss_filter.

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?

There is no guidance on when to use this tool versus alternatives like spss_filter or spss_if_transform. 'Permanently' implies a contrast with temporary filtering, but no explicit exclusions or alternatives are provided.

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