Spss Chart Area

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

No annotations are supplied, so the description carries the full burden. It does disclose the rendering path (GGRAPH + OMS) and that the result is an exported image file in one of three formats, which signals a file-writing side effect. It does not say where the file is written or returned, whether a dataset must already be open, or anything about the SPSS backend dependency.

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?

One tightly packed sentence with the resource and formats front-loaded and no filler. The 'via GGRAPH + OMS' clause is implementation detail but short and arguably informative about how SPPS renders it.

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?

A 10-parameter, no-annotation tool needs substantially more description than this; the output schema covers the return value, but the meaning of seven parameters and the destination of the exported file are undocumented. An agent would have to guess at data_file handling and sizing semantics before calling it correctly.

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 10 parameters, so the description must compensate and it only partly does. It adds meaning for x (time/ordinal) and y, and hints at image format via 'PNG/TIFF/EMF', but says nothing about data_file, dpi, width_px/height_px, title, x_label, or y_label.

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') and a specific resource ('area chart') plus the accepted output formats (PNG/TIFF/EMF), which is enough for an agent to know this produces an image rather than a statistic. It does not explicitly differentiate itself from near neighbours like spss_chart_line or spss_chart_bar, so the sibling routing is left slightly to inference.

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?

Usage is implied rather than stated: 'y against a time/ordinal x variable' tells the agent the data shape this chart suits, which functions as an implicit when-to-use condition. There is no explicit guidance on when to pick an area chart over spss_chart_line or spss_chart_bar, and no prerequisites or exclusions are named.

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