spss_graph_histogram

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

With no annotations provided, the description carries the full burden. It does disclose that normal_curve=True overlays the normal curve and that IBM SPSS Statistics is required, which adds useful behavioral context. However, it does not mention whether the tool creates a new output file, modifies anything, or how it behaves if the variable is invalid.

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 extremely short and front-loads the key concept ('Histogram'). Both sentences provide useful information without redundancy. It is appropriately concise, though it sacrifices explanatory depth.

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 low schema coverage and absent annotations, this definition is not complete enough for an agent to confidently invoke it. The description omits file_path semantics, title meaning, and any indication of the output behavior, even though an output schema exists.

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 for undocumented parameters. It explains normal_curve behavior and references the variable through the syntax, but it does not explain file_path or title at all, leaving two parameters semantically 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 clearly identifies the tool as producing a histogram and even gives the exact SPSS syntax ('GRAPH /HISTOGRAM[(NORMAL)]=var'). It is distinguishable from sibling graph tools like spss_graph_scatter, spss_graph_boxplot, and spss_graph_bar by name and the histogram-specific syntax, though it does not explicitly contrast itself with those siblings.

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_frequencies or spss_graph_bar. The only practical note is 'Requires IBM SPSS Statistics,' which is an environment requirement rather than usage guidance.

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