notebook_delete

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

Adds significant context beyond annotations: describes irreversibility and the exact two-step confirmation flow, including the fact that default call returns a preview without deleting. Annotations only declare destructiveHint, so this description enriches agent understanding of safety and side effects.

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?

Two compact paragraphs with the core action front-loaded. Every sentence adds essential behavioral detail; no filler or redundancy.

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 two-step delete tool with an output schema, the description fully explains the default preview behavior, the confirmation parameter, and irreversibility. It is complete for an agent to use correctly without additional context.

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 has 0% coverage, but description compensates by explaining that 'notebook' accepts a name or ID and that 'confirm' is a boolean defaulting to false, triggering preview vs actual delete. This gives functional meaning to both parameters.

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?

Begins with a specific verb+resource: 'Delete a notebook (irreversible).' Clearly distinguishes from siblings like notebook_create, notebook_list, and notebook_rename by stating the delete action. Also clarifies input type ('name or ID').

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?

Provides clear contextual guidance on the two-step confirmation process and how confirm=False vs true changes behavior. Does not explicitly name alternative tools for exclusion, but the resource-specific nature makes the use case unambiguous.

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