draw_clear

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

The description states the action but does not disclose potential side effects, permanence, or whether the action is undoable. Since no annotations are provided, the description carries the full burden, and for a destructive clear-all operation, more transparency (e.g., 'this cannot be undone') would be valuable.

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, front-loaded sentence with zero wasted words. It states exactly what the tool does.

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 parameterless mutation tool, the description adequately covers the operation. It clearly indicates scope ('all drawings') and requires no additional 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?

The tool has zero parameters, so the schema coverage is trivially 100%. Baseline 4 is appropriate; the description does not need to explain parameters.

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 'Remove all drawings from the chart' uses a specific verb ('Remove') and resource ('all drawings from the chart'), clearly distinguishing it from sibling tools like draw_remove_one (which removes a single drawing).

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 is provided about when to use this tool versus alternatives. It does not explicitly say 'use this to clear all drawings at once' or 'do not use this for individual removals', leaving the agent to infer from the name compared to draw_remove_one.

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