mne_plot_epochs_image

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

With no annotations, the description discloses that it plots and returns PNG paths, indicating a read-only, file-producing operation. However, it does not mention display behavior, backend requirements, or whether it modifies the Epochs object, leaving some ambiguity.

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?

A single sentence with no wasted words. It front-loads the core purpose and includes the return type, making it highly efficient.

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?

The output schema covers return values, so that part is accounted for. But the tool is underspecified for invocation: parameter semantics are missing, usage guidance is thin, and no annotation context compensates. An agent would struggle to use it correctly.

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% and the description mentions neither 'picks' nor 'name'. The property names give a weak hint, but no actual semantics are provided, so an agent cannot know what values to pass.

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 action ('Plot'), the specific resource ('an ERP image (epochs × time heatmap) for an Epochs object'), and the output ('Returns PNG path(s)'). This distinguishes it from sibling plotting tools like mne_plot_evoked or mne_plot_psd.

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 it should be used on an Epochs object, but provides no explicit alternative handling or when-to-use versus other plotting tools. It gives a prerequisite but no exclusions or comparisons.

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