spss_twostep_cluster

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 only discloses the prerequisite 'Requires IBM SPSS Statistics to be installed.' It does not mention side effects, whether it is read-only, how missing values are handled, or what the output looks like—leaving major behavioral gaps.

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 three concise sentences, front-loaded with the core purpose, followed by relevant capabilities and a prerequisite. There is no fluff or redundancy.

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?

Despite having an output schema, the tool is complex with 7 parameters and no annotations. The description offers only a high-level overview and one prerequisite, but lacks guidance on parameter selection, data preparation, or invocation context, making it incomplete for reliable use.

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 7 parameters with 0% description coverage, so the description must compensate. It hints at 'automatic cluster number determination' (implying num_clusters can be null) and 'mixed variable types' (implying continuous/categorical parameters), but does not explain any parameter names, ranges, or behaviors. This is insufficient for 7 parameters.

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 'Run two-step cluster analysis with automatic cluster number determination,' which is a specific verb+resource combination. It also distinguishes from sibling tools like spss_cluster_hierarchical by explicitly mentioning automatic clustering and mixed variable types.

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 when to use the tool: when handling large datasets, mixed variable types, and needing automatic cluster count. However, it does not explicitly exclude alternatives or name the hierarchical cluster tool as an alternative, so it lacks explicit when-not-to-use guidance.

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