obsidian_write_canvas

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

Annotations lack idempotent and destructive hints; description does not elaborate on behavior when overwrite is false and file exists, error handling, or side effects. Minimal behavioral disclosure beyond the basic write nature.

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?

Extremely concise single sentence with no extraneous text. However, it sacrifices useful detail that could be included without significantly lengthening the description.

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?

With 5 parameters, no output schema, and overlapping sibling tools, the description fails to clarify the canvas file format, required node/edge structure, or success/failure signals. The tool's complexity demands more context.

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 only 40%; the description only mentions 'nodes and edges' implicitly but adds no semantic detail for parameters like nodes, edges, or overwrite. It does not explain the expected structure of nodes/edges or the effect of overwrite=true/false.

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 creates or overwrites an Obsidian .canvas file from nodes and edges. It specifies the resource type (.canvas) and the input format, distinguishing it from other canvas-related tools like obsidian_canvas_create.

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 on when to use this tool versus alternatives such as obsidian_canvas_create or obsidian_canvas_patch. The description does not address prerequisites, limitations, or common scenarios.

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