notebooklm_delete_audio

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 does communicate that the operation is destructive, but it does not state whether deletion is permanent, whether it affects the notebook or its sources, or what happens after deletion. For a deletion tool, this is a significant transparency gap.

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 extremely concise and front-loaded with the verb 'Delete', with no wasted words. However, it borders on under-specification, so it is efficient but not richly informative.

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?

For a destructive tool with no annotations, no output schema, and only a one-line description, important context is missing: the scope of deletion, irreversibility, side effects, and expected return behavior. Agents may understand the basic action but cannot fully anticipate the consequences of calling this 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?

The schema already documents notebookId with 'Notebook ID' and has 100% description coverage, so the baseline is 3. The description adds no additional meaning about the parameter, such as where to find the ID or what values are valid.

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 uses a specific verb ('Delete') and a specific resource ('audio overview'), so the core action is unambiguous. It is distinguishable from siblings like notebooklm_generate_audio and notebooklm_delete_notebook by resource and action, but it does not explicitly name alternatives or clarify whether it deletes all audio overviews for the notebook or a specific one.

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?

There is no guidance about when to use this tool versus alternatives such as notebooklm_remove_sources or notebooklm_delete_notebook. No context, prerequisites, or exclusions are provided, so an agent receives no help choosing or invoking the tool appropriately.

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