create_canvas_page

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

With no annotations, the description must carry transparency. It does disclose that the page is 'new' and 'empty' and that the tool returns an id, but it doesn't mention side effects, prerequisites, or whether h/w dimensions can be adjusted later. Some behavioral context is given, but not exhaustive.

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 extremely concise, with two sentences that front-load the core purpose and then give actionable next steps. Every phrase adds value, and there is no redundant repetition of schema information.

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 simple creation tool, the description covers the essential context: what is created, the returned id, the immediate next step (set_canvas), and how to size the canvas (using list_devices). It stops short of explaining parameter default behavior or required name, but the schema covers those basics.

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 coverage is 0%, so the description must compensate for parameter meaning. It explains that h and w are for sizing to the target panel and points to list_devices, but it does not specify units or fully describe the name parameter. Name is self-evident from the schema, but the description adds limited detail beyond the parameter 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: 'Create a new, empty canvas dashboard and return its id.' It specifies the resource ('canvas dashboard') and distinguishes it from sibling tools like set_canvas, which is for layout, and list_pages, which is for viewing existing pages.

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 provides clear usage context: use this tool to create the empty page first, then follow up with set_canvas() for layout, and size the page using list_devices. It doesn't explicitly state when not to use this tool or alternative creation methods, but the workflow guidance is strong.

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