spss_chart_histogram_density

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

No annotations are provided, so the description carries the full transparency burden. It discloses the technical mechanism ('via GGRAPH + OMS') and the output nature ('Export'), but it omits important behavior such as what OMS does (e.g., suppressing table output), file handling details (naming, overwriting), or behavior when the variable is not continuous. The description is not misleading but is under-specified for a tool with no annotation safety net.

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 a single, front-loaded sentence that states the action, output, and key input requirement. Every word adds value, and there is no irrelevant filler. It is appropriately concise for a focused chart-export tool.

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?

With 9 parameters, 0% schema coverage, and no annotations, the description must carry a heavy load but only covers the core purpose and one input. It does not explain the data_file parameter, default behaviors, or how the output is returned (although an output schema exists, that doesn't cover input semantics). The description is too sparse to enable correct use in varied contexts.

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 adds meaning for the variable parameter ('Provide a continuous variable'). Parameters like data_file, dpi, width_px, height_px, image_format, and labels are left entirely to their names, which may be self-explanatory for some but not all (e.g., data_file). The description fails to compensate for the lack of schema descriptions.

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 a specific action ('Export a publication-ready histogram overlaid with a normal density curve') and distinct output formats (PNG/TIFF/EMF), which differentiates it from sibling tools like spss_chart_histogram that likely produce a simpler histogram without the density overlay. The verb 'Export' and resource specification are precise.

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 instruction 'Provide a continuous variable' gives a clear prerequisite for use. The description implies when to use it (when a histogram with normal density is needed) but does not explicitly name alternatives or exclusions, such as 'use spss_chart_histogram if you don't need the density curve.' Overall, the context is clear but 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.