duplicate_notebook

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

With no annotations provided, the description fully carries the transparency burden. It discloses background execution (never switches active tab), notification to user, cell ID regeneration, clearing of last-run results, and the label/placement behavior. This is rich, honest behavior disclosure.

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 three sentences, front-loaded with the core purpose, then progressively adds details. Every sentence contributes unique information: what is copied, the background behavior, and the conditional for activate_notebook. 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?

For a tool with one parameter, no output schema, and no annotations, the description comprehensively covers behavior, side effects, user experience, and edge-case instruction. It leaves no critical gaps for an agent to misuse the 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 single parameter buffer_id has 100% schema coverage, so the schema already describes it. The description refers to 'the original' and 'source' implicitly but does not add additional parameter-level meaning beyond the schema. Baseline 3 is appropriate.

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's function: 'Duplicate a notebook tab' with a specific verb and resource. It distinguishes from siblings like duplicate_cell and create_notebook by detailing what gets copied (cells, layout), the naming convention, and placement right after the original.

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?

It gives clear context for when to use (duplicating a notebook) and explicitly cautions against calling activate_notebook unless the user asks to be taken to the copy. However, it does not explicitly mention alternatives like create_notebook for blank notebooks, so it lacks exhaustive when-not guidance.

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