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 for behavioral disclosure. While it mentions the prerequisite condition (research_status must be 'completed'), it doesn't describe what 'import' actually does operationally - whether it copies, moves, or transforms data; what permissions are required; whether it's idempotent; what happens if sources are already imported; or what the output looks like. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence serves a purpose - the first states what the tool does, the second provides crucial timing context, and the Args section documents parameters. However, the parameter documentation could be more integrated with the main description rather than in a separate Args section.

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 this is a mutation tool with no annotations, 3 parameters (2 required), 0% schema description coverage, but WITH an output schema, the description is moderately complete. The timing prerequisite is valuable, and parameter explanations help, but for a tool that presumably modifies notebook state by importing research sources, more behavioral context about what 'import' entails would be beneficial despite the existence of an output schema.

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?

With 0% schema description coverage, the description partially compensates by explaining all three parameters in the Args section: notebook_id as 'Notebook UUID', task_id as 'Research task ID', and source_indices as 'Source indices to import (default: all)'. This adds meaningful context beyond the bare schema, but doesn't provide format details (like what constitutes valid indices) or explain the relationship between task_id and the research process mentioned in the description.

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 ('Import discovered sources') and target ('into notebook'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'notebook_add_drive' or 'notebook_add_url' which also add content to notebooks, leaving some ambiguity about how this tool differs from those alternatives.

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 timing guidance ('Call after research_status shows status="completed"'), which is excellent context for when to use this tool. However, it doesn't mention when NOT to use it or provide alternatives for similar operations, nor does it explain the relationship with the 'research_start' sibling tool that presumably initiates the research process.

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