editor_clear_errors

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

With no annotations, the description carries full burden. It clearly indicates a mutating action (clearing the error list), which implies destruction of the list contents. However, it does not mention whether the action is reversible, affects only the current session, or has any side effects on the editor's state.

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 without any wasted words. It directly states the tool's purpose and nothing else.

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 zero-parameter, simple mutation tool, the description is sufficient. It clearly identifies the target (editor error list) and the action (clear). While there is no output schema, the tool likely returns no meaningful value, so additional detail is not necessary.

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 is complete with 100% coverage. The description does not need to explain parameter semantics because there are none, which is appropriate for a parameterless tool.

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 the specific verb 'Clear' with a clear resource, 'the editor error list.' It is distinct from sibling tools like editor_get_errors (which retrieves errors) and compile_shader (which generates errors).

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 no guidance on when to use this tool versus alternatives, such as editor_get_errors, nor any context about prerequisites or situations where clearing the error list is appropriate. It simply states the action.

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