write_obsidian_note

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

With no annotations, the description must fully disclose behavior. It only says 'Write' but does not state whether existing files are overwritten, directories are created, what happens if no active vault exists, or what the response contains. The vault_path parameter's effect is also undisclosed.

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, succinct sentence with no redundant words, front-loading the verb and object. However, its brevity omits necessary context, which is a weakness rather than a strength in this case.

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?

This tool has 3 parameters, no annotations, and an output schema that is not described. The one-sentence description fails to explain key operational aspects like vault_path's role, content formatting, overwrite behavior, or interaction with set_vault_path, making it unsafe for an agent to invoke correctly.

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 makes no mention of any parameter (content, note_path, vault_path). Since schema description coverage is 0%, the description provides no additional meaning beyond the schema's bare field names.

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 action ('Write'), the object ('a markdown note'), and the destination ('into the active Obsidian vault directory'). This specific verb+resource combination differentiates it from siblings like set_vault_path and get_codebase_structure, even though siblings are not explicitly referenced.

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., setting the vault path) or exclusions. The word 'active' hints at prior configuration but is not explained.

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