clear_input

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It simply says 'Clear' but does not mention that maxChars limits deletion to a maximum (default 100), meaning the field may not be fully cleared if it exceeds that length. It also omits behavior when no field is focused, such as whether it errors or does nothing.

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, well-structured sentence with no wasted words. It front-loads the action and object, making it immediately scannable and easy to understand.

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 tool with one optional parameter and no output schema, the description is minimally adequate but incomplete. It fails to clarify the maxChars default limitation or the behavior when there is no focused input, which could lead an agent to invoke it incorrectly or misinterpret the result.

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 single parameter maxChars is already fully documented in the input schema with type, range, and default. The description adds no further meaning about how this parameter affects the clearing behavior, so it meets the baseline but does not exceed it.

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 a precise resource ('currently focused text input field'), making the tool's function immediately clear. It distinguishes itself from siblings like type_text or set_text by targeting only the focused input.

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 implies when to use the tool—when a text input is focused and needs to be cleared—but it does not explicitly state when not to use it or mention alternatives such as set_text for replacing content. The context is understandable but not fully elaborated.

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