Read Android logcat

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds minimal extra behavioral context beyond stating it 'reads' and uses adb. It does not describe potential blocking, buffer clearing, or return format details.

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 two sentences long, front-loaded with the primary function, and efficiently includes use cases. No unnecessary words or fluff.

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 tool's simple nature and schema coverage, the description is adequate. It mentions use cases and the basic operation. However, it could briefly note that output is limited by maxLines and that filters apply, though these are clear from the schema. No output schema exists, so the description could hint at the output format.

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%, so baseline is 3. The description does not add any additional meaning beyond the parameter descriptions in the schema. It does not explain nuances like tagFilter pattern or minLevel enum semantics.

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 clearly specifies the action (reads), the resource (logcat output from connected Android device/emulator), and the use cases (diagnosing crashes, ANRs, runtime errors, tracing logs). It distinguishes itself from sibling tools like devilge_take_screenshot and devilge_list_devices.

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?

The description explicitly states when to use the tool (diagnosing crashes, ANRs, etc.) but does not provide explicit when-not-to-use or mention alternatives among siblings. The context is clear enough for an agent to decide.

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