Delete a note

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

The description adds significant behavioral context beyond annotations: it explains the trash behavior, the irreversibility of permanent deletion, and the confirm parameter to skip confirmation. Annotations only indicate destructiveness; description fills in the details.

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 sentences, front-loaded with the primary action, then optional detail. No superfluous text. Every sentence earns its place.

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?

No output schema, but descriptions of behavior and confirm parameter are adequate. Could mention error handling (e.g., note not found), but for a delete tool this is sufficient. Context signals show moderate complexity (5 params), and description covers key behavioral aspects.

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 100%, so baseline is 3. Description adds value by explaining the effect of 'permanent' (irreversible) and 'confirm' (skip confirmation). This goes beyond schema descriptions.

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 that the tool moves a note to trash or permanently deletes it. The verb 'delete' and resource 'note' are specific, and it distinguishes from siblings like obsidian_create_note or obsidian_append_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 implies when to use the tool (to delete notes) and provides options (permanent vs trash). It does not explicitly exclude scenarios or mention alternatives, but the context is clear enough given sibling tools are mostly different operations.

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