obsidian_prepend_daily_note

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

No annotations, so the description carries the full behavioral burden. 'With revision check' is a useful hint at optimistic concurrency, but it never says what happens on a revision mismatch (error? overwrite? no-op?), whether the note is created if missing, or what permissions are needed for a write operation.

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 compact sentence with the verb and resource front-loaded and no wasted words. Brevity comes at the cost of substance, but nothing is padded.

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 mutation tool with no annotations, no output schema, and zero schema description coverage, far too little is specified. An agent cannot tell where in the note text lands, whether the daily note is auto-created, or how the revision check affects retries.

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% and the description is silent on all three parameters. 'Daily note' weakly implies the date parameter, and 'revision check' gestures at expectedRevision, but neither the date format nor the meaning/source of the revision string is explained beyond what the schema's pattern already shows.

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?

Specific verb (prepends) plus resource (the daily note), which distinguishes it from obsidian_append_daily_note and obsidian_prepend_note. It does not explicitly say it targets the date-stamped daily note versus a named note, but the resource is clear enough to route by name.

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?

No guidance on when to choose this over obsidian_append_daily_note, obsidian_prepend_note, or obsidian_update_note. The only contextual cue is the word 'daily', leaving the append-vs-prepend-vs-update decision to inference.

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