clear_logcat

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

No annotations exist, so description carries full burden. It honestly describes the destructive effect (empties buffer) and the impact on subsequent logcat reads (every line read is caused by the action). Does not mention prerequisites (adb connection) but is otherwise transparent for this simple mutation.

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 concise sentences plus a parenthetical alternative. Front-loaded with action, no filler words. Every sentence earns its place.

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?

Given the simple tool (1 optional param, no output schema), the description covers purpose, usage, effect, and alternative. No gaps. The isolation primitive analogy provides rich context.

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 100% for the single 'serial' parameter, with adequate explanation in schema. Description does not add parameter-specific semantics beyond the schema, so baseline 3 is appropriate.

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?

Description uses specific verb 'Empty' and resource 'logcat ring buffer', clearly stating the action. It distinguishes from sibling tools like logcat (read) and start_logcat_capture (capture to file) by focusing on clearing the buffer as an isolation primitive.

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?

Explicitly explains when to use: as the sharpest isolation primitive for a press→observe loop. Provides when-not-to-use context (filter hits may be seconds old, empty result may mean buffer rotated). Names an alternative: 'use logcat's since param' for reaching back in time.

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