Mne Plot Topomap

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

With no annotations, the description carries the burden. It discloses that the tool returns a PNG path, which implies file creation, but it doesn't mention whether the operation is read-only, where the file is saved, or any side effects on session state. This is partial behavioral disclosure.

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?

Two sentences with no redundant words. The main action is front-loaded, followed by the essential times parameter format, and ends with the return value. Every sentence earns its place.

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 tool is simple and an output schema exists, but the description lacks clarity on the 'name' parameter and doesn't mention whether an Evoked must already exist in the session. Defaults make a basic call possible, but an agent may not know how to point to a specific Evoked.

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?

The schema description coverage is 0%, so the description must compensate. It fully explains the 'times' parameter's valid values ('auto', 'peaks', comma-separated seconds), but the 'name' parameter is not described at all, leaving the agent to infer it refers to an Evoked object in the session.

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 action (plot scalp topographies) and resource (an Evoked), which clearly distinguishes it from sibling tools like mne_plot_evoked or mne_plot_epochs_image. It also specifies the times argument options, making the tool's scope unambiguous.

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 (when you need topomaps of an Evoked) but gives no explicit guidance on when to choose this over alternative plotting tools, nor does it mention exclusions or prerequisites. The times parameter format is useful but doesn't cover tool selection.

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