Duplicate Excalidraw canvas

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Copies a canvas', which implies a new resource is created, but it does not explain conflict behavior when newCanvasPath already exists, the role of baseRevision and mutationId, or whether the operation is reversible or has side effects.

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, short sentence with no filler, and the core action is front-loaded. It is concise, though it sacrifices helpful behavioral detail that other dimensions require.

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?

For a mutating tool with five required parameters, no annotations, and no output schema, the description is too minimal. It omits details about concurrency semantics, overwrite behavior, return values, and error conditions, making it incomplete for an agent to invoke confidently.

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 60%, and the description adds no parameter-level meaning. The required baseRevision and mutationId parameters are left unexplained both in the schema and in the description, leaving an agent without enough information to supply them correctly.

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 action ('Copies a canvas') and a clear scope ('inside the same project'). This distinguishes it from duplicate_project, but it does not explicitly differentiate it from other canvas-copying siblings like save_canvas_copy.

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 same-project scope implies when this tool is appropriate, but the description gives no explicit guidance about when to use it versus alternatives such as save_canvas_copy or duplicate_project. There are no exclusions or conditions stated.

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