origin_plot_contour

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

With no annotations, the description carries the full burden but only states it imports and creates, offering no details on side effects, permissions, error cases, or data handling. The agent learns little beyond the basic action.

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 two sentences and no superfluous words. However, it sacrifices necessary detail for brevity, slightly reducing effectiveness.

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?

With 21 parameters and a complex task, the description is grossly incomplete. It fails to clarify required parameters, output expectations, or contouring behavior, despite an output schema being available.

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?

Given 0% schema coverage of parameter descriptions, the description adds minimal value by hinting at 'XYZ table data' (implying x_col, y_col, z_col) but does not explain the other 17 parameters. The agent is left guessing parameter meanings.

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 verb (import and create) and resource (XYZ table data and contour graph), distinguishing it as importing tabular data rather than matrix data, which differentiates from siblings like origin_plot_matrix_contour. However, it does not explicitly contrast with similar tools.

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, such as origin_plot_contour vs origin_plot_matrix_contour. The agent must infer usage solely from the name and description.

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