logcat_clear

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

No annotations are provided, so the description carries the full behavioral burden. It never states that this is a destructive, irreversible operation that discards existing buffered logs, nor whether it affects all devices or only the default/serial-specified one.

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 front-loaded sentence with the operation and the equivalent adb command; no filler.

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?

An output schema exists so return values need not be explained, and the tool is simple. However, for an unannotated destructive operation with an undocumented parameter, the description leaves notable gaps about scope and effect.

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 0% and the single `serial` parameter is undocumented in both schema and description. The description adds no meaning about how to target a specific device or what the null default implies.

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?

Names a specific verb (Clear) and resource (device logcat ring buffers), and the parenthetical `logcat -c` pins down the exact underlying operation, distinguishing it implicitly from logcat_stop and logcat_dump. It stops short of explicitly contrasting with those siblings.

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?

There is no statement of when to clear versus when to use logcat_start/logcat_stop/logcat_dump, nor any prerequisite or context. The agent must infer that this resets the buffer before a capture.

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