Open File In Obsidian

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

The description states 'mutates the UI but does not touch file contents', which complements annotations (readOnlyHint=false, destructiveHint=false). It also mentions the Local REST API dependency. No contradiction with annotations.

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?

Three concise sentences: purpose, parameter behavior, and context. Each sentence serves a clear purpose without redundancy.

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?

Given the output schema exists and the tool has only two straightforward parameters, the description covers all necessary aspects: prerequisites, parameter behavior, and side effects.

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 coverage is 100%, so the description adds minimal new meaning beyond what the schema already provides. It reiterates the newPane behavior but doesn't add semantic depth.

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 specifies 'Open a vault-relative note path in the live Obsidian UI' which clearly states the verb, resource, and context. It distinguishes from workspace tools like activeFile and closeActiveFile.

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 includes explicit guidance: 'Requires the Local REST API plugin' and clarifies that vault.select does not affect this tool. It also explains the newPane parameter behavior.

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