NotebookLM MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Add') which implies a write operation, but does not describe permissions needed, whether the operation is idempotent, error conditions, or what happens on success (e.g., if the document becomes linked or copied). This leaves significant gaps in understanding the tool's behavior.

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 front-loaded with the core purpose in the first sentence, followed by a structured 'Args:' section that efficiently lists parameters with brief explanations. Every sentence adds value without redundancy, making it easy to scan and understand quickly.

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 the tool has an output schema (which handles return values), no annotations, and 4 parameters with 0% schema coverage, the description does well by explaining all parameters and the tool's purpose. However, it lacks details on behavioral aspects like error handling or integration effects, which are important for a write operation with no annotation support.

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 adds meaningful context for all parameters: 'notebook_id' as Notebook UUID, 'document_id' as Drive document ID from URL, 'title' as display title, and 'doc_type' with enum values (doc|slides|sheets|pdf). This clarifies the purpose and format of each parameter beyond the basic schema types.

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 specific action ('Add Google Drive document as source'), identifies the resource (Google Drive document), and distinguishes it from siblings like 'notebook_add_text' and 'notebook_add_url' by specifying the document source type. It provides a verb+resource combination that is precise and unambiguous.

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 implies usage by specifying the tool adds a Google Drive document as a source, suggesting it's for integrating external documents into notebooks. However, it lacks explicit guidance on when to use this tool versus alternatives like 'notebook_add_url' or 'source_sync_drive', and does not mention prerequisites or exclusions.

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