canvas_layer_add

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

No annotations are provided, so the description bears full responsibility. It states the tool 'Adds' a node and returns success/error, but does not disclose side effects, prerequisites (e.g., scene must be open), or behavior if the layer name already exists. The description lacks sufficient behavioral context.

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 concise with two sentences plus an argument list. It is well-structured with 'Args:' and 'Returns:' sections, making it efficient and easy to parse.

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 that an output schema exists (per context signals), the description need not detail return values, but it mentions 'Success message or error description.' It covers the basic operation but omits edge cases or error conditions. For a simple creation tool, it is minimally complete.

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 0%, but the description lists all 5 parameters with brief explanations (e.g., 'layer_order: Layer rendering order (higher values render on top, default: 0)'). This adds meaning beyond the schema's titles and types, compensating for the lack of parameter descriptions.

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?

Description clearly states 'Add a CanvasLayer node to organize UI elements by depth,' which is a specific verb-resource pair. It includes the category CanvasLayer and differentiates from siblings like canvas_layer_configure (modify) and canvas_layer_set_order (set order) by implying creation.

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 implies usage for creation via 'Add,' but it does not explicitly state when to use this tool versus alternatives like canvas_layer_configure or canvas_layer_set_order. No exclusions or context for selecting this tool are given.

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