clear_canvas

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'clear all elements' but does not disclose whether the action is irreversible, whether it clears undo history or presentational attributes, or if any confirmation is required. The destructive nature is implied but not explicit, which is a significant gap for a mutation tool.

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, concise sentence with no filler words. It communicates the action and target resource efficiently, earning a perfect score for conciseness.

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 tool with zero parameters and no annotations, the description is minimal. While it adequately conveys the basic function, it omits crucial context such as irreversibility, potential impact on undo history or associated resources, and return value. Given the destructive nature, this is a noteworthy gap that a more complete description should address.

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?

The tool has zero parameters, so the schema provides full coverage by definition. The description adds no parameter-specific detail, but none is needed. According to the rubric, 0 parameters warrant a baseline of 4, and the description does not detract from this.

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 'Clear all elements from the canvas' uses a specific verb ('clear') and resource ('canvas'), explicitly stating the scope ('all elements'). This distinguishes it clearly from sibling tools like 'delete_element' which removes a single element, and 'query_elements' which reads data.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that this is a bulk/clear-all operation and should be preferred over 'delete_element' or 'batch_create_elements' when the entire canvas needs resetting, nor does it list any exclusions or prerequisites.

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