delete_notebook

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

Discloses that the notebook is moved to trash (not permanently deleted), restorable for 30 days, and requires optimistic locking. Without annotations, the description fully covers the behavioral traits.

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, each conveying essential information without redundancy, front-loading the core action and supporting details efficiently.

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 simple tool with two required parameters and no output schema, the description adequately covers the operation's effect (trash, restore window), locking requirement, and configuration flag. Missing details on auth or error handling, but still sufficient.

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 already has 100% coverage with descriptions for both 'id' and 'version'. The description reemphasizes the version's role in optimistic locking but adds no new semantic meaning beyond the schema, meeting the baseline for high coverage.

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 'Delete (trash) a notebook by id' with a specific verb and resource, and distinguishes it from sibling tools like 'create_notebook' and 'update_notebook' by mentioning 'WRITE' and optimistic locking.

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?

Explicitly mentions the prerequisite 'DT_ENABLE_WRITES=true' and the need to supply the current document version for optimistic locking, giving clear context for use. However, it lacks explicit when-not-to-use or alternative tools for permanent deletion.

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