Spss Chart Scatter

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

No annotations are provided, so the description carries more burden. It discloses useful implementation context (GGRAPH + OMS IMAGE) and that a chart file path is returned, but it does not mention permissions, whether existing files are overwritten, or other operational behavior.

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 sentences, front-loaded with the core action and output, with no wasted words. The essential information is immediately clear.

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?

For a tool with 10 parameters and no annotations, the description is too sparse. It covers the basic required inputs and output path, but leaves most parameter meanings and behavioral details 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%, so the description should compensate but only mentions x and y. It adds no meaning for the other 8 parameters such as dpi, title, labels, dimensions, data_file, or image_format.

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 states a specific verb (Export), a clear resource (scatter plot), and the output formats (PNG/TIFF). It distinguishes this tool from sibling chart tools like spss_chart_histogram or spss_chart_bar by naming the chart type.

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?

It says to provide x and y variables, but gives no guidance on when to choose a scatter plot over other chart types or any preconditions. Usage is only implied by the tool name and required inputs.

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