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. 'Show or update a task' implies both read and write capabilities, but it doesn't specify permissions needed, side effects, rate limits, or what 'update' entails (e.g., toggling status). This leaves critical behavioral traits unclear for a tool with potential mutations.

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 extremely concise with a single sentence 'Show or update a task.' It's front-loaded and wastes no words, though this brevity contributes to underspecification rather than clarity.

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's complexity (10 parameters, no annotations, no output schema), the description is completely inadequate. It doesn't explain what the tool does in detail, how to use parameters, what it returns, or how it fits with siblings, making it insufficient for effective agent use.

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 mentions no parameters, while the input schema has 10 parameters with 0% description coverage (only titles like 'Vault', 'Ref'). This fails to compensate for the schema's lack of detail, leaving all parameters semantically undefined and unusable without guesswork.

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 'Show or update a task' states a vague purpose with two possible actions but lacks specificity about what resource it operates on (Obsidian tasks) and how it differs from sibling tools like obsidian_tasks. It's better than a tautology but doesn't clearly distinguish the tool's unique function.

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 like obsidian_tasks or other task-related tools. There's no mention of prerequisites, context, or exclusions, leaving the agent with no usage direction.

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