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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is partly covered. The description adds useful behavioral context beyond annotations: missing folders are created, existing notes are never replaced, and Obsidian's settings folder is never written. It does not discuss authentication or rate limits, but the added constraints are valuable.

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 three tightly written sentences with no filler. The core operation is front-loaded, followed by mode behavior and safety constraints in a logical order.

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?

An output schema exists and annotations cover the mutation safety profile, so the description need not explain return values. It covers the operation, modes, and key constraints well. Explicit sibling-tool routing, such as when to use this instead of create_note or update_note, is the main missing piece.

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 100%, so the schema already documents all five parameters, including the ignored confirm flag. The description clarifies mode semantics and some path behavior indirectly, but it does not add parameter-specific meaning beyond what the schema provides.

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 states a specific verb and resource: writes a Markdown note in an Obsidian vault. It also defines the two modes, create and append. It does not explicitly distinguish itself from sibling tools such as create_note or update_note, so it falls short of a 5.

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 clearly explains when to use mode="create" versus mode="append". It does not name alternative sibling tools or state when not to use this tool, but the mode-selection context is clear.

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