bardo_note_delete

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

The description goes beyond annotations by detailing the grace period, immediate disappearance vs. actual purge, recoverability, and lock condition with error code. This adds significant context beyond the destructiveHint annotation.

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?

Three sentences front-loaded with the core action, followed by behavioral nuance and error handling. No superfluous words; every sentence contributes essential information.

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?

The description covers behavior, side effects, error case, and recovery, but omits explanation of the session_token parameter and does not specify the response (though no output schema exists). It is nearly complete for the tool's complexity.

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?

With 0% schema coverage, the description should explain parameters. It implicitly references note_id in the workaround but does not describe it or session_token explicitly, leaving the agent to infer parameter purpose from context.

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 note (the whole thing, all versions together).' It specifies the resource (note) and scope (all versions), distinguishing it from siblings like bardo_note_undelete and bardo_note_update.

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?

The description provides guidance on when not to use (if locked) and an alternative (unlock via bardo_note_update). It also hints at a recovery path (bardo_note_undelete). However, it does not explicitly contrast with other note-related tools or state preferred use cases.

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