eic_plot_chromatograms

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

The description adds useful behavior beyond readOnlyHint=true: it returns only structured lipidmix.eic.v1 JSON, does not render images or write files, and is client-neutral. It also states a 12-trace limit for file_ids. It does not fully explain the returned JSON shape or several parameters.

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 front-loaded with the purpose and then adds constraints in a compact, readable way. Every sentence contributes useful routing or behavioral information without unnecessary repetition.

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?

For a read-only plotting-data tool with no output schema and low parameter description coverage, the description does well to explain output format and file behavior. However, it omits meaning for title, file_path, and especially normalize, and does not describe the structured JSON content enough for an agent to fully anticipate the response.

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%, so the description must carry parameter meaning. It explains spot_id as exact and sourced from search tools, and file_ids as selecting at most 12 traces, but it does not explain title, file_path, or normalize, leaving three of five parameters undocumented.

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 states a specific verb and resource: return client-neutral plot data for selected EIC chromatograms. It clearly distinguishes this from image rendering and save_figure, but does not explicitly differentiate it from the sibling eic_plot_compounds tool.

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?

It gives explicit usage guidance: use for structured EIC plot data, do not use for rendering or writing files, and call save_figure(kind="eic") only after an explicit PNG request. It also says spot_id normally comes from existing m/z or RT search tools and explains file_ids selection behavior.

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