Start Android logcat

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the risk profile is covered. The description usefully adds that the process is persistent and returns a session handle for cursor reads, but says nothing about the effect of clearFirst on the device log buffer or session lifetime limits.

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 no filler; the action and outcome come first. Slightly informal phrasing ("normal Raccoon process session") costs a point.

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 6-parameter session-creating tool with no output schema and destructive annotations, the description should cover parameter behavior, session lifecycle, and cleanup; it covers none of these beyond stating that a session is returned.

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?

Six parameters with 0% schema description coverage, and the description names none of them — filters, clearFirst, maxLogBytes, serial, deviceId are all unexplained, so an agent must guess formats and the destructive effect of clearFirst.

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?

States a specific verb and resource ("Start persistent adb logcat") and clarifies the return artifact is a Raccoon process session used for cursor reads, which distinguishes it from one-shot sibling tools like adb_shell or process_read.

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?

Implies usage via "persistent" and "for cursor reads" (stream/keep reading logs), but never states when to choose this over process_start/read_process_output or when to stop it (stop_search, kill_process). Only implicit routing guidance.

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