save_to_obsidian

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

No annotations are provided, so the description must disclose all behavioral traits. It does not mention that this tool is a write operation (could overwrite existing files), schema constraints (e.g., content size limits, character limits), or whether it requires specific configuration or authentication. This leaves the agent with critical unknowns.

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 a single, clear sentence that front-loads the key action and resource. It is concise with no wasted words, though it could benefit from minor behavioral disclosure without losing efficiency.

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 simplicity (2 params, no nested objects, no enums, no output schema) and lack of annotations, the description should be more complete. It does not explain return behavior, overwrite semantics, or note location, leaving significant gaps for an agent to determine success or errors.

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 input schema has 100% coverage with descriptions for both parameters: 'title' is 'Title of the note' and 'content' is 'Markdown content to save.' The description itself does not add new meaning beyond the schema, so a baseline score of 3 is appropriate given perfect schema coverage.

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 saves a session summary or custom markdown note into a configured Obsidian Vault. The verb 'saves' and the resource 'Obsidian Vault' are specific, and the description distinguishes it from siblings like search_obsidian_memory which searches rather than saves.

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 implies this tool is for saving notes, but it does not explicitly state when to use it versus alternatives like search_obsidian_memory. No exclusions or when-not-to-use guidance is provided, which would help the agent avoid misuse.

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