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 the confirm requirement for user approval, which is a key behavioral trait. However, it doesn't mention other important behaviors like whether this is a read/write operation, potential side effects, rate limits, or what happens when source_ids is null. The description adds some value but leaves significant gaps.

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 structured with a purpose statement followed by parameter explanations. However, it could be more front-loaded - the key requirement about user approval is buried. Some sentences like 'Generate report' are overly terse, while the parameter explanations are clear but could be more efficiently integrated.

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 6 parameters with 0% schema coverage and no annotations, the description does a good job explaining parameter semantics and the confirm requirement. The presence of an output schema means the description doesn't need to explain return values. For a report generation tool with multiple parameters, this provides adequate context though more behavioral transparency would help.

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 must compensate for 6 parameters. It provides meaningful context for all parameters: notebook_id as UUID, source_ids default behavior, report_format options, custom_prompt requirement, language as BCP-47 codes, and confirm's purpose. This adds substantial value beyond the bare schema, though it doesn't explain parameter interactions in depth.

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 report' with specific parameters like notebook_id and report_format. It distinguishes from siblings by focusing on report generation rather than other content types like flashcards, quizzes, or mind maps. However, it doesn't explicitly differentiate from similar tools like 'slide_deck_create' or 'infographic_create' which might also generate content from notebooks.

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 usage context: 'Requires confirm=True after user approval' and specifies when custom_prompt is required. It implicitly suggests this is for report generation from notebooks, but doesn't explicitly state when to use this vs. alternatives like 'slide_deck_create' or 'quiz_create' for different output formats.

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