Create Canvas

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

Annotations are minimal (all false), so description carries full burden. It details creation behavior, overwrite mechanism, and vault path handling. No contradictions. Could add more on side effects (e.g., file system write) but sufficient.

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?

Four sentences covering purpose, failure, alternative, and vault context. No excess words, front-loaded with key action. Highly efficient.

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 output schema exists (not shown), description doesn't need to detail return. Covers creation, failure, overwrite, and vault. Could mention that canvas files are JSON but that's contextual. Completeness is high for a file creation tool.

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?

Description reinforces filePath and overwrite semantics from schema, and adds meaning for vaultPath (override of session vault) beyond its schema description (which is missing). Schema coverage 67% is partially compensated.

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?

Clearly states it creates a new empty Obsidian canvas file at a given path. Distinguishes from sibling tools (canvas.edit) and specifies conditions (fails if exists unless overwrite). Verb 'create' and resource 'Obsidian canvas file' are explicit.

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?

Provides when to use (create a new canvas) and when not to use (if path exists without overwrite). Points to alternative 'canvas.edit' for adding nodes/edges. Also explains vault context and how vaultPath overrides session vault.

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