notebook_delete

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

No annotations provided, so description carries full burden. It clearly states the action is permanent and irreversible, and that confirm must be true. This covers the key behavioral traits for a delete tool, though could mention effects on shared access.

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?

Extremely concise: two sentences plus argument list. Front-loaded with the critical behavior 'Delete notebook permanently. IRREVERSIBLE.' Every sentence adds value.

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 simplicity of a delete tool with output schema, the description covers the essential behavior and parameter requirements. Could optionally mention return value or error cases, but not necessary for functionality.

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 coverage is 0%, so description must compensate. It adds meaning by describing notebook_id as 'Notebook UUID' and confirm as 'Must be True after user approval'. This is basic but sufficient; could elaborate on UUID format or how to obtain it.

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 notebook permanently' with 'IRREVERSIBLE', specifying the verb and resource. It distinguishes from sibling tools like notebook_create or notebook_rename by emphasizing permanence.

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 requires confirm=True after user approval, guiding proper invocation. Lacks explicit when-not-to-use or alternatives, but the confirmation requirement effectively communicates the safety gate for a destructive operation.

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