notebook_delete

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

Emphasizes 'permanently' and 'IRREVERSIBLE', clearly conveying the destructive nature. Without annotations, this is essential. However, lacks details on permissions, cascading effects, or return value.

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 with a single sentence plus a shout-out to irreversibility. All information is front-loaded and no words are wasted.

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 destructive tool with a confirm parameter, the description adequately states the key effect. However, it could mention what happens if the notebook doesn't exist, confirm usage, and access requirements. Lacks output schema guidance.

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 description adds no value beyond the schema. 'notebook_id' has no schema description and is not elaborated in the tool description. 'confirm' is already described in schema. Schema coverage is 50% but description doesn't compensate.

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 action 'Delete a notebook permanently' and distinguishes it from sibling tools like notebook_create, notebook_rename, etc. The resource and operation are explicit.

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?

No guidance on when to use or alternative approaches (e.g., soft delete, trash). Lacks context on prerequisites or when not to use this tool.

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