library.remove

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

Annotations already set destructiveHint=true, and the description adds that it is 'Dangerous' and requires user confirmation. It also clarifies that it does not delete the actual NotebookLM notebook, providing extra behavioral context beyond annotations.

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 well-structured with a clear warning, numbered steps, and an example. Every sentence adds value, and the information is front-loaded with the danger warning.

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 output schema exists and annotations cover idempotency and destructiveness, the description fully covers purpose, usage, and behavioral aspects. It leaves no gaps for a safe and correct invocation.

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?

Input schema has 100% coverage with a single parameter 'id' described as 'The notebook ID to remove'. The description adds value by explaining the workflow that involves looking up the full name before using this ID, but does not elaborate on the parameter itself. Baseline 3 is elevated due to workflow context.

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 removes a notebook from the library, with the annotation title 'Remove notebook from library'. The verb 'remove' is specific and distinguishes it from sibling tools like library.add or notebook.delete.

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 instructions: only call after user requests removal, after confirming the full name, and only on explicit 'Yes'. It also states 'Never remove without permission', giving clear when-to-use and when-not-to-use guidance.

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