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 effectively communicates the destructive nature ('IRREVERSIBLE') and the confirmation requirement, which are critical for safe use. However, it lacks details on permissions, rate limits, or error handling, leaving some behavioral aspects unspecified.

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 action and warning, followed by concise parameter explanations. Every sentence adds value: the first states purpose and risk, the second outlines usage rules, and the args section clarifies parameters without redundancy. It is efficiently structured with zero 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 the tool's complexity (destructive operation, 2 parameters) and no annotations, the description does well by covering purpose, irreversible risk, and confirmation requirement. With an output schema present, return values need not be explained. However, it could mention prerequisites like authentication or error scenarios for full completeness.

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 semantics: 'notebook_id' is explained as a 'Notebook UUID', and 'confirm' is clarified with 'Must be True after user approval', providing context beyond the bare schema. This covers both parameters adequately, though it could detail format constraints for the UUID.

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 ('Delete'), resource ('notebook'), and critical characteristic ('permanently'), which distinguishes it from sibling tools like notebook_rename or notebook_describe. It specifies the irreversible nature upfront, making the purpose explicit and distinct.

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 usage guidance: it states 'Requires confirm=True' and 'Must be True after user approval', indicating when to use this tool (only after user confirmation) and implying when not to use it (without approval). This is clear and directive for safe invocation.

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