mne_get_info

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

No annotations are provided, so the description must disclose behavior. 'Show' indicates a read-only operation, and it specifies the output as 'full channel list and measurement info.' However, it does not mention prerequisites (e.g., a loaded session), side effects, or error conditions. The output schema covers return structure, so this is adequate but not rich.

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 one sentence, front-loaded with the verb, and contains no redundant information. Every word 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?

For a simple one-parameter read tool with an output schema, the description covers what it does and what the parameter refers to. It doesn't need to explain return values due to the output schema. It could mention session prerequisites, but 'for a named session object' adequately implies an existing object. Overall, it is complete for the tool's simplicity.

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 single 'name' parameter is only described as 'a named session object' in the description. This gives semantic meaning (identifies the session), but it doesn't elaborate on the naming format or how to obtain the session name. Schema coverage is 0%, so the description partially compensates but not fully.

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 'Show' with a specific resource: 'the full channel list and measurement info'. It scopes to 'a named session object,' which distinguishes it from sibling tools like mne_session_info and mne_check_status. However, it doesn't explicitly compare with alternatives, so it's not a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance. The purpose is clear enough that a user can infer to use it when needing channel list or measurement info, but no alternatives or exclusions are mentioned. This is implied usage, not explicit guidance.

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