AxPlotToData_extract_numerical_series

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

No annotations are provided, so the description carries full burden. It mentions 'precise numerical data points' but does not disclose limitations such as accuracy, supported plot types (only line/scatter implied), behavior with noisy data, or output format. The description is too brief to adequately inform an agent about behavioral traits.

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 a single sentence, front-loaded with the verb 'Analyzes' and resource. It is concise with no wasted words, but could benefit from more structure if expanded. For its length, it is efficient and clear.

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 no output schema and no annotations, the description is incomplete. It does not explain return values, error handling, or limitations beyond the schema. For a tool of moderate complexity (2 parameters), more context is needed to understand what the tool produces and how it handles edge cases.

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%, so baseline is 3. The tool description adds no extra meaning beyond what the schema already provides for plot_path and max_number_points_per_series. No additional context is given for parameter interpretation.

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 analyzes images of line and scatter plots to extract numerical data points from all series. The verb 'analyzes' and resource 'images of line and scatter plots' are specific, and the purpose distinguishes it from siblings like AxPlotToData_split_multi_plot which splits multi-plot images.

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 implies usage for extracting data from all series in a plot but does not provide explicit guidance on when to use this tool versus alternatives like split_multi_plot or when not to use it. No exclusions or context for selection are mentioned.

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