Clear A2UI Surfaces

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description does not need to repeat those. It adds useful scope ('all surfaces') and clarifies that state is reset, but it does not mention irreversibility or data-loss consequences beyond what 'clear' implies.

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?

A single, compact sentence with no filler. The action and scope are front-loaded, making it immediately understandable.

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 parameterless destructive reset operation, the description combined with the annotations is sufficient. It could mention that the action is irreversible or affects all surfaces, but 'clear all surfaces and reset the state' already conveys the essential behavior.

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 and the schema provides 100% coverage, so the baseline of 4 applies. The description cannot add parameter-level meaning, and none is needed here.

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') with an explicit resource ('all A2UI surfaces') and the resulting effect ('reset the state'). This clearly distinguishes it from sibling tools like a2ui_get_state or a2ui_update_components.

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 phrase 'clear all' implies this is for a full UI reset rather than incremental updates, but the description does not explicitly state when to use it versus alternatives or when it should be avoided. Usage guidance is inferred, not stated.

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