note_save_chat

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

The description discloses that it extracts all messages and saves them as a formatted note with timestamps and attribution. This adds context beyond annotations (readOnlyHint=false, indicating a write operation) and does not contradict them.

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 purpose statement, a process paragraph, a bulleted use-case list, and a note on output content. It is concise, though the use-case list could be slightly more compact.

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 low parameter complexity (3 optional params) and the presence of an output schema, the description adequately covers purpose, process, use cases, and output content. It does not address edge cases like empty chats, but overall is complete.

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 input schema covers all three parameters with descriptions, achieving 100% coverage. The description adds minimal extra context, such as the default title 'Chat Summary', but does not significantly enhance parameter understanding beyond the schema.

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 saves the current chat to a note, using the verb 'Save' and specifying the resource 'current NotebookLM chat/discussion'. It distinguishes from sibling tools like note_create (which creates a blank note) by specifying it extracts messages from a chat.

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 explicitly lists three use cases: preserving conversations, creating summaries, and saving history. It implies when to use this tool over alternatives, though it does not explicitly state when not to use it.

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