clear_logcat

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

With no annotations, the description carries the burden. It clearly states the destructive effect (clearing/flushing buffers) and the practical intent (discarding logs). However, it doesn't mention irreversibility, device scope, or any prerequisites, leaving some behavioral gaps.

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, focused sentences. The first states the action and resource; the second explains when to use it. No redundant or filler content.

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 one-parameter destructive tool with no output schema, the description is sufficient: it names the action, the resource, and a typical use case. The optional serial parameter is explained in the schema, and the description's 'all current' clarifies scope.

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 schema already covers the single optional parameter 'serial' with a description, giving 100% coverage. The tool description adds no extra meaning about this parameter, which is acceptable at the baseline but not enhanced.

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 specific verbs ('Clear', 'flush') and identifies the exact resource ('all current logcat buffers'), clearly distinguishing this destructive action from read-only siblings like get_logcat.

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?

It provides a clear use case: run before a test to discard old irrelevant logs. It doesn't explicitly mention alternatives or when not to use it, but the context is unambiguous for a simple utility tool.

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