NotebookLM MCP Server

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

With no annotations provided, the description carries full burden. It discloses that the tool requires user confirmation ('confirm=True after user approval'), which is a crucial behavioral constraint. However, it doesn't mention whether this is a read-only or destructive operation, what permissions are needed, or what happens to existing mind maps. The description adds some behavioral context but leaves significant gaps for a creation tool.

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 reasonably concise with two sentences, but the structure is inefficient. The first sentence states the purpose and constraint, while the second sentence lists parameters with brief explanations. However, the parameter explanations are terse and could be better integrated. The description avoids redundancy but doesn't optimally front-load the most critical information.

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 that there's an output schema (which handles return values), no annotations, and 4 parameters with 0% schema coverage, the description is moderately complete. It covers the purpose, a key behavioral constraint (confirmation), and lists parameters. However, for a creation tool that likely produces persistent artifacts, it should better explain what 'Generate' entails, what resources are consumed, and provide more parameter context to compensate for the schema coverage gap.

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%, so the description must compensate. It lists all 4 parameters but provides minimal semantic context: 'notebook_id: Notebook UUID' and 'source_ids: Source IDs (default: all)' add some meaning, while 'title: Display title' and 'confirm: Must be True after user approval' are somewhat helpful. However, critical details are missing: what format UUIDs should be, what 'Source IDs' refer to, what happens when source_ids is null, or what 'user approval' entails.

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 ('Generate and save mind map') and resource ('mind map'), making the purpose evident. It distinguishes from sibling 'mind_map_list' by focusing on creation rather than listing. However, it doesn't specify what exactly is being generated from (e.g., notebook content), leaving some ambiguity compared to other creation tools like 'infographic_create'.

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 provides explicit guidance on when to use the tool: 'after user approval' with 'confirm=True'. This establishes a clear prerequisite condition for invocation. However, it doesn't mention when NOT to use it or explicitly differentiate from similar creation tools like 'infographic_create' or 'quiz_create' that might also work with notebooks.

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