obsidian_open_daily_note

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

No annotations provided; description only states 'Open or create' without detailing prerequisites (e.g., Obsidian must be running) or side effects (e.g., what template is used, whether it focuses the app).

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?

Extremely concise: two sentences plus a bullet list of args/returns. No redundant words, front-loaded with the core action.

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?

Lacks essential context: does not explain what a daily note is (typically date-based), whether Obsidian must be running, or the exact return format beyond 'Success message or error'. Insufficient for an agent unfamiliar with Obsidian.

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?

With 0% schema coverage, the description adds value by explaining that 'vault' is a name or ID, but does not elaborate on how to obtain vault names or provide examples, leaving the agent with minimal guidance.

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?

Clearly states the action (open or create) and the specific resource (the daily note in Obsidian), which distinguishes it from sibling tools that deal with generic notes or other operations.

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 use this tool versus alternatives like obsidian_create_note or obsidian_open_note_in_app. Does not mention that this is specifically for the current day's note.

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