origin_plot

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

No annotations provided, so description carries full burden. It discloses how selected_cols maps columns (first as X, rest as Y, one-column as Y-only), but does not address potential side effects like overwriting existing graphs, permissions, or rate limits. Moderate transparency.

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 concise with six sentences, front-loading the core purpose, and each sentence provides necessary context without redundancy.

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 complexity (7 params, 2 required, many kinds) and presence of output schema, the description covers key usage aspects and behavioral details. Minor gap: no mention of whether plots are created on new or existing graphs (addressed partially in graph_name param).

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 100%, baseline 3. Description adds significant value beyond schema by explaining how selected_cols interprets column order (X vs Y), which is not detailed in the parameter descriptions.

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 creates a table-based plot selected by kind, uses specific verb 'Create' and resource 'table-based plot', and distinguishes itself from sibling tools like dedicated origin_plot_* tools and matrix plot routes.

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?

The description explicitly explains when to use this tool vs dedicated origin_plot_* tools (single parameterized entry point) and mentions that matrix-range plots still use origin_plot_matrix_id, providing clear alternatives.

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