adb_logcat_clear

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

No annotations are present, so the description bears full responsibility for disclosing behavior. It states 'clear' which implies a destructive operation, but it does not explain what happens to the data, whether it is irreversible, or any required permissions. The description lacks important behavioral details for an agent to assess side effects.

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, direct sentence with no extraneous information. It is appropriately concise and front-loaded, conveying the core action immediately.

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 tool that modifies state (clears buffers), the description is too minimal. It does not mention what buffers are cleared, whether the device must be in a specific state (e.g., logcat running), or what the outcome is. Given the complexity of logcat operations and the presence of multiple sibling tools, more context is needed for an agent to use this correctly.

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% (the single parameter 'device' has a description 'Device serial'), so the description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate; no extra semantic value provided.

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 'Clear all logcat buffers on the device' uses a specific verb 'clear' and a clear resource 'logcat buffers' with scope 'all'. It effectively distinguishes from sibling tools like adb_logcat (which reads logs) and adb_logcat_start/stop (which control logging sessions).

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?

No guidance is provided on when to use this tool versus related tools (e.g., adb_logcat, adb_logcat_stop). There is no mention of prerequisites, alternatives, or conditions under which clearing buffers is appropriate. The description only states the action without context.

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