origin_plot_scatter

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

No annotations are provided, and the description only mentions generic 'import and create'. It omits behavioral traits such as whether it modifies existing graphs, supports multiple data sources, or requires a specific Origin environment.

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 sentence and not verbose, but it is too brief for a tool with many parameters. It front-loads the action but sacrifices necessary detail, making it inefficient for use.

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 tool's complexity (22 parameters, no annotations, no output schema details), the description is severely incomplete. It fails to cover data import sources, plot customization, error bars, or export behavior, leaving major gaps.

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?

With 22 parameters and 0% schema description coverage, the description adds no semantic value beyond the schema. It fails to explain any parameter's purpose, default behavior, or valid values, leaving the agent to guess.

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 the tool imports table data and creates a scatter graph. However, it does not differentiate from sibling scatter-related tools like origin_plot_auto or origin_plot_line, lacking explicit distinction.

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 on when to use this tool versus alternatives like origin_plot_line or origin_plot_from_range. No context on prerequisites, data format requirements, or typical use cases.

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