slipbox_delete_note

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

With no annotations, the description carries the full burden. It discloses that deletion is permanent and also removes all links to and from the note. This is critical behavioral information beyond the basic delete action, making the tool's effects transparent.

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 concise and well-structured: main action first, followed by a warning and alternative suggestion, then a simple args list. Every sentence provides useful information without 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 simple delete operation with one parameter and no output schema, the description covers the core action, the permanent effect, cascading link removal, and an alternative. This is sufficiently complete for an agent to select and invoke the tool appropriately, given the sibling 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?

The schema description coverage is 0%, so the description must compensate. However, the only parameter documentation is 'note_id: The ID of the note to delete', which merely restates the parameter name without adding meaningful semantic detail (e.g., format, how to obtain the ID, or constraints). This adds minimal value over the raw schema.

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 a note permanently' with a specific verb and resource. It also differentiates from the update alternative by suggesting 'updating note_type to fleeting' for uncertain cases, which distinguishes it from sibling tools like slipbox_update_note.

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 explicit guidance on when to avoid this tool: 'Consider updating note_type to fleeting instead if uncertain.' This clearly tells the agent when not to use deletion and points to an alternative action, serving as a usage guideline.

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