NotebookLM MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by specifying the confirm requirement for user approval, which hints at a mutation operation needing consent. However, it lacks details on side effects (e.g., what gets created, rate limits, or response format), leaving gaps for a tool with 7 parameters and output schema.

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 appropriately sized and front-loaded with the core purpose and confirm requirement in the first sentence. The Args section is structured but includes some redundancy (e.g., repeating 'default: all' and enum values already in schema). Overall, it's efficient with minimal waste.

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 7 parameters with 0% schema coverage, an output schema exists (so return values needn't be explained), and no annotations, the description is moderately complete. It covers all parameters briefly and includes the confirm requirement, but lacks behavioral context like what the video overview entails or error conditions, making it adequate but with clear gaps for a complex tool.

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 7 parameters with brief explanations (e.g., 'Notebook UUID', 'Source IDs (default: all)'), adding meaning beyond the bare schema. However, explanations are minimal (e.g., 'BCP-47 code' without examples beyond en/es/fr/de/ja), and it doesn't clarify interactions like how source_ids=null differs from an empty array, leaving significant gaps.

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 purpose as 'Generate video overview' with specific parameters like notebook_id and format, making the verb+resource combination explicit. However, it doesn't distinguish this tool from sibling tools like 'slide_deck_create' or 'infographic_create' beyond the 'video' aspect, missing sibling differentiation.

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 clear context with 'Requires confirm=True after user approval', indicating when to use this tool (after approval) and implying a prerequisite. It doesn't explicitly state when not to use it or name alternatives among siblings, but the approval requirement offers practical guidance.

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