mne_install_backend

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

No annotations are provided, so the description fully carries the burden. It discloses that this is an installation into the server's Python environment, mentions the large download and multi-minute duration, and explains profile differences. This gives the agent a realistic picture of the operation's impact.

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 compact yet comprehensive. Every sentence serves a purpose: what it does, when to use it, the profile options, and expected duration. Information is front-loaded, with the core purpose in the first clause.

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 the tool's moderate complexity (installation with profile choices) and lack of annotations, the description covers all essential aspects: purpose, trigger condition, parameters, side effects, and time. An output schema likely handles return values, so those need not be described. There are no notable gaps for an agent to invoke this 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?

The schema has only one parameter (profile) with no description (0% schema coverage). The description adds full semantics by listing the three valid values and their meanings: 'ica' (default), 'analysis' (no scikit-learn), and 'full' (adds source localization, connectivity, etc.). This is exactly the kind of value the description should add.

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's function: provisioning the MNE-Python backend into the server's environment. It uses a specific verb ('Provision') and resource ('analysis backend'), and is distinct from sibling analysis tools like mne_filter or mne_plot_raw.

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?

Explicit usage guidance is provided: 'Call this once when mne_check_status reports the backend is not installed'. It also clarifies that after calling, every mne_* tool works without client restart, setting a clear condition for use.

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