Add markdown content to daily, weekly, monthly, quarterly, or yearly notes in Obsidian, keeping journals and period-based logs updated in one step.
Append content to a periodic note (e.g. add an entry to today's daily note).
| Name | Required | Description | Default |
|---|---|---|---|
| period | Yes | The period type for the note | |
| content | Yes | Markdown content to append |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden for a write operation. It states 'append,' which hints at additive, non-destructive behavior, but says nothing about what happens if the periodic note does not yet exist, where in the note content lands, or whether the call is idempotent.
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?
A single, well-formed sentence with the core action front-loaded and the parenthetical example earning its place by disambiguating 'periodic note.' It is efficient, though arguably terse given the tool's open behavioral questions.
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?
With no annotations, no output schema, and a write action, the definition leaves an agent unable to determine key preconditions: whether the target note must be created first, whether content is appended at the end, and what the result looks like. The sibling set (create_periodic_note, get_periodic_note) suggests relevant context that is never addressed.
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 100% and the period parameter is an enum, so the schema already documents both parameters fully. The description only illustrates 'daily' via the example and adds no syntax or format detail beyond the schema, which makes the baseline 3 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 gives a specific verb (append) and resource (periodic note) and clarifies 'periodic note' with a concrete example, 'add an entry to today's daily note.' It implicitly separates this from the generic sibling append_to_note, though it never names an alternative explicitly.
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?
Usage is only implied by the example; there is no statement of when to prefer this over append_to_note, append_to_active_note, or create_periodic_note, nor any precondition (e.g. whether the periodic note must already exist). A sibling named create_periodic_note makes that omission meaningful.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.