spss_descriptives

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns specific statistics and requires IBM SPSS Statistics to be installed, which is useful. However, it does not mention what happens with invalid variables, missing values, or how optional statistics behave.

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 concise sentences front-load the action and output. Every word contributes value, and no redundant information is present.

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 output schema likely covers return values, so the description's mention of returned statistics is enough on that front. However, the parameter semantics gap for file_path and the vague 'optional statistics' leave the tool under-specified for correct 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?

Schema description coverage is 0%, and the description only hints at 'variables' being numeric and 'optional statistics' existing. It does not explain file_path, the format of variables, or what statistics values are accepted, leaving significant ambiguity for correct invocation.

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 tool runs SPSS DESCRIPTIVES for numeric variables and lists the computed statistics (N, mean, std deviation, min, max, optional statistics). This specific verb-resource pairing distinguishes it from siblings like spss_frequencies and spss_correlations.

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 provides clear context: use for numeric variables and requires SPSS installed. It does not explicitly mention alternatives or when not to use, but the numeric-variable scope effectively implies its primary use case.

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