blender_annotation_clear

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

No annotations are provided, so the description carries the burden of explaining behavior. 'Clear' conveys that annotation data is removed, and the description discloses the all-vs-specific behavior, but it does not mention side effects such as irreversibility, whether the layer itself is deleted, or what happens if the specified layer does not exist.

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?

Two short, front-loaded sentences communicate the core operation and the two modes with no filler. Every sentence earns its place.

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 single-optional-parameter tool with no output schema, the description is mostly complete. It covers the main two behaviors, though it omits minor details like error handling for non-existent layers and the exact nature of what is cleared.

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 100%, and the schema already explains that omitting layer_name clears all annotation layers. The description adds no meaning beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb ('clear') and resource ('annotation layers'), and clearly distinguishes the operation from sibling tools like blender_annotation_add, blender_annotation_text, and blender_annotation_dimension. It also clarifies the two supported scopes: a named layer or all layers.

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 intended use is implied: clear annotation layers when annotations need to be removed. However, there is no explicit when-to-use vs. alternatives, no prerequisites, and no mention that this should not be used for deleting/creating annotation layers or for editing annotation content.

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