Delete Note

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

The description adds meaningful behavioral context beyond the destructiveHint annotation by clarifying the nuanced safety net (trash vs permanent deletion). It also reinforces the requirement for explicit user intent before irreversible deletion, which is critical for an AI agent.

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 succinct and front-loaded: the main purpose is stated in the first four words, and the second sentence adds crucial usage guidance without any fluff. Every word 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?

For a destructive tool, the description fully covers the essential behavioral nuance (trash vs permanent) that an agent needs to know. The schema handles parameter details, and no output schema exists, so no further return-value explanation is required. The tool is simple, and the description is complete for its scope.

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 input schema already covers 100% of parameters with clear descriptions (path with example, permanent with 'Requires explicit user intent'). The description mentions 'permanent=true' but does not add significant semantics beyond what the schema provides, so the baseline of 3 for high schema coverage is appropriate.

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 opens with 'Delete a note', which is a specific verb+resource combination that clearly distinguishes this tool from its siblings like obsidian_create or obsidian_read. It unambiguously communicates the tool's primary action.

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: 'By default moves to trash; set permanent=true only when the user explicitly asks.' This clearly states when to use the default behavior versus the permanent deletion flag, offering a when-not that helps avoid accidental data loss.

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