origin_plot_line

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

No annotations are provided, so the description must convey behavioral traits. It only states creation of a line graph but does not disclose whether it modifies existing graphs, side effects, permissions, or resource impact. This is insufficient for a complex tool.

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 very short (one sentence), which is concise but under-specified for a tool with 22 parameters and many siblings. Important information is missing, making it less useful than a more balanced length.

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?

The tool has high complexity (22 parameters, no annotations, no schema descriptions). The description fails to cover essential context like file types, column specifications, or return behavior. It is not nearly complete enough for reliable agent usage.

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 0% schema description coverage and 22 parameters, the description adds no parameter meaning. The agent cannot infer what 'path', 'x_col', 'y_cols', etc., require without external knowledge. This is a critical gap.

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 line graph. It distinguishes from sibling tools (e.g., origin_plot_scatter, origin_plot_histogram) by specifying 'line graph', making the purpose unambiguous.

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 alternative plotting tools. It lacks context about prerequisites, data formats, or scenarios where tool is appropriate, leaving the agent without decision support.

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