spss_star_join

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the join intent and software requirement. It does not disclose whether an output file is created, whether existing output_path is overwritten, what join semantics apply (e.g., inner vs. outer), or what happens on key mismatches.

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 tight sentences deliver the operation, syntax pattern, key parameter semantics, and a prerequisite without filler. The core join behavior is front-loaded, and every sentence earns its place.

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 is too thin for an 8-parameter tool with no annotations and no schema property descriptions. Even though an output schema exists, the description omits important operational context like join direction, output file behavior, alias purposes, and constraints on key variables, making it inadequate for confident invocation in edge cases.

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 description adds genuine meaning for base_key/join_key as matching variable names and for select_fields with a concrete alias-qualified example. However, schema description coverage is 0%, and the description leaves base_file, join_file, output_path, base_alias, and join_alias to inference from names/defaults, so it only partially compensates for the schema gap.

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 identifies a specific operation—an SQL-style join of two .sav files using STAR JOIN syntax—so an agent can tell what resource it acts on. It stops short of a 5 because it does not explicitly differentiate itself from the closely related sibling spss_match_files.

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 this tool over alternatives such as spss_match_files or spss_add_files. The only contextual signal is the prerequisite 'Requires IBM SPSS Statistics,' which addresses environment constraints rather than use-case selection.

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