origin_plot_3d_errorbar

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

No annotations provided. Description only states the basic action without disclosing side effects (e.g., creates new graph vs. adds to existing), required permissions, or response behavior. Insufficient for a mutation 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?

Single sentence is concise and front-loaded. It states core purpose without extra words, but could be slightly expanded to include key parameter hints without losing conciseness.

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 5 parameters, no output schema details, and many sibling tools, the description is too sparse. It does not explain return values, how error bars are specified, or relationship to other plot types. Incomplete for effective use.

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%. Description does not explain any of the 5 parameters (path, selected_cols, graph_name, title, export_path). 'From table data' hints at path but adds no specifics.

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?

Description clearly states 'Create a 3D scatter plot with error bars from table data', which is a specific verb+resource. It distinguishes this tool from sibling 3D plot tools (e.g., origin_plot_3d_scatter, origin_plot_3d_bars) by specifying 'error bars'.

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 phrase 'from table data' gives context about input source but does not explicitly state when to use this tool versus alternatives like origin_plot_3d_scatter or origin_plot_errorbar (2D). No exclusion or alternative guidance.

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