obsidian_append_note

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

No annotations are provided. The description indicates that the tool modifies a note (append is destructive) but lacks details about file locking, error handling, or performance. The return value is mentioned as 'Success message or error' but not elaborated.

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 extremely concise: one sentence stating the operation followed by a compact parameter list. Every sentence is useful, no fluff, and the action is front-loaded.

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 tool is simple with 3 required params and no enums. The description covers the basic operation and parameter roles. However, given 39 sibling tools, the lack of usage guidance or behavioral context leaves gaps for an agent to decide correctly.

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 description coverage is 0%, but the description adds brief explanations for each parameter (vault as name or path, path as note path, content as content to append). This adds meaning beyond the schema's bare types, though not deeply detailed.

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 'Append content to the end of an existing note,' specifying a clear verb (append) and resource (existing note). This distinguishes it from siblings like obsidian_prepend_note and obsidian_write_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 usage for appending content to existing notes but does not explicitly state when to use this tool versus alternatives like prepend or write. No guidance on when-not-to-use or context for selection.

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