Obsidian MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides almost none. 'Load a saved workspace' implies a read operation but doesn't clarify whether this changes application state, what happens if the workspace doesn't exist, whether authentication is required, or what the expected outcome is. For a tool that presumably restores a workspace configuration, this is a significant behavioral information 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 maximally concise at just 4 words. It's front-loaded with the core action and doesn't waste words. While it's under-specified, it's not verbose or poorly structured. Every word in 'Load a saved workspace' contributes to the basic meaning, even if that meaning is insufficient.

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 complexity of workspace operations, no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It doesn't explain what a 'workspace' is in this context, what gets loaded, what the expected outcome is, or any behavioral characteristics. For a tool that presumably restores application state, this leaves critical questions unanswered about side effects, error conditions, and return values.

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 description provides zero information about parameters, while the schema has 0% description coverage. With 2 parameters (one required 'name', one optional 'vault'), the description doesn't explain what these parameters mean, what values they accept, or how they affect the loading operation. The schema only provides titles 'Vault' and 'Name' without descriptions, so the description fails to compensate for the complete lack of parameter documentation.

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 'Load a saved workspace' is a tautology that essentially restates the tool name 'obsidian_workspace_load'. It specifies the verb 'load' and resource 'saved workspace', but doesn't clarify what 'workspace' means in this context or what the loading operation actually does. While it distinguishes from some siblings like 'obsidian_workspace_save', it doesn't clearly differentiate from other workspace-related tools like 'obsidian_workspace' or 'obsidian_workspaces'.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a saved workspace first), doesn't specify when this tool is appropriate versus other workspace tools, and offers no context about typical use cases. Given the sibling tools include 'obsidian_workspace', 'obsidian_workspaces', and 'obsidian_workspace_save', the lack of differentiation is particularly problematic.

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