origin_plot_3d_scatter

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

Annotations are absent, and the description provides no behavioral traits beyond the basic action. It does not disclose whether the tool creates a new graph or adds to an existing one, nor does it mention error handling, requirements, or side effects.

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 concise (one sentence, 9 words) but lacks necessary detail for a tool with 21 parameters. It front-loads the core purpose but is under-specified, earning a middle score.

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 (21 parameters, many optional, no annotations, and an output schema not shown here), the description is insufficient. It does not cover the variety of configuration options, data import capabilities, or formatting features, leaving significant gaps in the agent's understanding.

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%, meaning no parameter descriptions exist. The description only hints at 'XYZ table data' for the required x_col, y_col, z_col. None of the 17 optional parameters (e.g., graph_name, template, export_path) are explained, leaving the agent without guidance on their purpose.

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 it imports XYZ table data and creates a 3D scatter graph, distinguishing it from 2D scatter and other 3D plot types like surface or bars. However, it does not differentiate from the similar sibling 'origin_plot_matrix_3d_scatter', which also produces a 3D scatter but from matrix 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 over alternatives. With many sibling 3D plot tools, the description does not mention prerequisites, data format requirements, or scenarios where this tool is preferred.

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