Spss Chart Histogram Density

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

With no annotations, the description carries full behavioral burden. It discloses the output artifact type and formats and the underlying GGRAPH + OMS mechanism, which is useful. However it says nothing about authentication, file destination, overwrite behavior, or what happens if the variable is non-continuous.

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 with the core purpose and output format front-loaded, followed by the key input constraint. No wasted words.

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?

An output schema exists, so return values need not be explained. But for a 9-parameter chart-export tool with 0% schema coverage and no annotations, the definition leaves the majority of tunable behavior undocumented.

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% across 9 parameters, so the description must compensate, but it only identifies the required 'variable' parameter. Nine configurable options (dpi, width_px, height_px, image_format, title, x_label, y_label, data_file) are left entirely unexplained.

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?

States a specific verb (Export), the resource (histogram overlaid with a normal density curve), the output formats (PNG/TIFF), and the implementation backend (GGRAPH + OMS). The 'density curve' overlay clearly distinguishes it from the sibling spss_chart_histogram.

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?

'Provide a continuous variable' gives one usage constraint, implying this is for continuous data. But there is no guidance on when to choose this over spss_chart_histogram or the other chart siblings, and no when-not-to-use conditions.

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