obsidian_launch_app

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

The description discloses only the minimal behavior of launching the app. It does not mention what happens if the app is already running (e.g., brings to front vs. error), any required permissions, platform restrictions, or side effects. With no annotations, this represents a significant gap.

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 very short (2 sentences plus Args/Returns), which is concise but lacks substance. It is front-loaded with the core purpose but fails to provide necessary detail within the space.

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 tool is a simple launch action with one optional parameter, the description is incomplete. It does not explain return values beyond vague 'Success message or error', nor does it specify behavior when the app is already running or when the vault is invalid.

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%, so the description must compensate. It only notes 'Optional vault name to open on launch', which adds minimal meaning beyond the parameter name. It does not explain format, validation rules, or what happens if the vault does not exist.

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 clearly states the tool launches the Obsidian application and optionally opens a specific vault. It uses specific verbs ('Launch') and resource ('Obsidian application'), and distinguishes from sibling tools like obsidian_focus_app (which focuses rather than launches) and obsidian_check_app_running (which checks state).

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. For instance, it does not specify whether the app should be closed before launching, or if launching is only needed when the app is not running. There are no exclusion criteria or comparisons with siblings.

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