obsidian_append_to_daily_note

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

The description discloses non-obvious behavior not in annotations: it auto-creates the note, resolves the path from OBSIDIAN_DAILY_FOLDER and OBSIDIAN_DAILY_FORMAT, and can operate through filesystem or REST backends. It also describes the success and failure return shape. Basic safety hints are already in annotations, so this is a meaningful addition without contradiction.

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 front-loaded with the core action and then uses compact Args/Returns sections. It is scannable with minimal filler, though some of the Args detail is redundant with the schema.

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 description covers the key operational details: date defaulting, heading requirement, path construction, backend flexibility, and return/error shape. The only notable gap is the omitted vault parameter, but that is clearly documented in the schema, so the definition as a whole is sufficiently complete.

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's top-level 'params' property has no description (0% coverage), and the description's Args section repeats much of what the nested schema already documents. More importantly, it completely omits the 'vault' parameter, which is present in the schema, so an agent relying on the description could miss a supported option.

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 states a precise verb and resource: 'Append to the daily note for today or a given date, creating it if needed.' This clearly distinguishes it from the general obsidian_append_to_note sibling because it specifically targets the daily note and mentions creation and date handling.

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 clear context such as when the daily note is created and that it works regardless of Obsidian running. However, it does not explicitly say when to prefer this tool over obsidian_append_to_note or when not to use it, leaving alternative routing to inference.

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