Mne Get Info

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

With no annotations provided, the description carries the behavioral burden. The verb 'Show' clearly signals a read-only inspection operation with no mutation or destructive side effects, which is the key behavioral trait an agent needs. It does not mention error behavior or assumptions about session existence, but for a simple getter this is adequate.

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?

One compact sentence with no filler or redundancy. The action and target are front-loaded, and every word contributes to the meaning.

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 one-parameter, read-only information tool with an output schema present, the description covers the essential scope and return content. It is missing explicit usage differentiation from similar sibling tools, but overall the agent has enough to call it correctly in a straightforward inspection scenario.

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 input schema only declares a string parameter named 'name' with 0% description coverage. The phrase 'named session object' adds the essential semantic that 'name' identifies the target session object, which is meaningful beyond the raw schema. It does not specify expected name format or how to discover valid names, but the single-parameter simplicity limits the gap.

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 uses a specific verb ('Show') and names the resource ('full channel list and measurement info') plus the scope ('named session object'). It is clear what the tool returns, though it does not explicitly differentiate itself from siblings like mne_session_info or mne_describe.

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 gives no guidance on when to prefer this tool over sibling inspection tools such as mne_session_info, mne_describe, or mne_get_config. No exclusions, prerequisites, or alternative-selection conditions are provided.

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