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. It effectively explains what the tool does (reads image files for analysis), what it returns (Image object that Claude can analyze), and distinguishes it from related operations. However, it doesn't mention potential limitations like file size constraints, supported formats beyond what's in the schema pattern, or error conditions.

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 well-structured with clear sections (purpose, when to use, when not to use, returns) and every sentence adds value. It's front-loaded with the core purpose and efficiently organized without wasted words. The bullet-point format enhances readability while maintaining conciseness.

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?

For a read operation with no annotations and no output schema, the description provides good context about what the tool does, when to use it, and what it returns. It covers the essential aspects well, though it could benefit from mentioning potential error cases or limitations. Given the straightforward nature of an image reading tool, the description is largely complete.

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 67% (2 of 3 parameters have descriptions). The description doesn't explicitly discuss parameters, but the 'path' parameter's purpose is implied through the tool's overall purpose. The 'include_metadata' and 'ctx' parameters aren't mentioned, but with moderate schema coverage and the tool's straightforward purpose, the description provides sufficient context for understanding the primary parameter's role.

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's purpose with specific verb ('Read') and resource ('image file from the Obsidian vault'), and distinguishes it from sibling tools by specifying it's for standalone images rather than embedded ones. The opening sentence 'Read an image file from the Obsidian vault for analysis' provides immediate clarity about the tool's 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 explicit 'When to use' and 'When NOT to use' sections with clear alternatives named (view_note_images and list_notes). It gives specific scenarios for appropriate use (analyzing specific image files, examining standalone images) and explicitly contrasts with sibling tools for different use cases.

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