origin_plot_auto

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

With no annotations, the description carries full burden but only states it chooses a route and creates a plot. It discloses no behavioral details such as whether it modifies data, requires user interaction, or how the auto-selection works.

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 overly concise (one sentence) to the point of being insufficient. While it avoids verbosity, it sacrifices necessary information for effective 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 (23 parameters, many siblings) and lack of annotations or parameter descriptions, the tool description is severely incomplete. It does not explain what 'choose a chart route' entails or how the output is produced.

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 coverage is 0% and the description adds no meaning to the 23 parameters. The agent cannot infer the role of parameters like path, intent, x_col, or style_mode from the description alone.

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 it chooses a chart route and creates a plot, which gives a general sense of the tool's purpose. However, 'chart route' is ambiguous and does not distinguish it from sibling plot tools that also create plots from table data.

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 is provided on when to use this tool versus other plot tools like origin_plot_scatter or origin_plot_line. The description does not specify conditions where auto selection is beneficial or alternatives.

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