note_create

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

The annotations already indicate readOnlyHint=false and idempotentHint=false, so the core behavioral traits are covered. The description adds that notes support markdown formatting, but does not disclose further behavioral aspects such as duplicate handling, size limits, or response structure. Given the annotation coverage, this is adequate but not exceptional.

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 concise: three sentences, with the purpose front-loaded. Every sentence adds context without redundancy. No wasted words.

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 that the tool has 4 parameters with 100% schema coverage, an output schema, and sibling tools, the description covers the purpose and usage context well. It lacks some behavioral details (e.g., idempotency, conflicts) and direct sibling differentiation, but remains functional for a simple create operation. Overall, it is mostly 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no new information beyond what the schema already provides for each parameter. It restates that content supports markdown, which is already in the schema. Therefore, no additional value.

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 starts with a clear verb-resource pair: 'Create a note'. It specifies the location (NotebookLM Studio panel) and explains the role of notes as user-created annotations. This distinguishes it from sibling tools like note_save_chat and note_to_source, which have different actions.

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 explains that notes are for saving research findings, summaries, etc., providing context on when to use this tool. However, it does not explicitly contrast with similar sibling tools like note_save_chat or note_to_source, missing an opportunity for clearer guidance.

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