logcat_start

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

No annotations, so the description carries the burden. It discloses that capture is backgrounded, writes to a temp file, and only one runs at a time – useful. However it omits what 'clear' does (wipes existing buffer before starting?), whether start fails/no-ops when a capture is already running, and permission requirements.

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?

Three short sentences, zero filler, front-loads the action and then the workflow. The buffers note is placed last where it belongs.

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?

Covers lifecycle and concurrency well, and an output schema exists so return values need not be explained. Gaps remain around the semantics of `clear` and `serial`, and the exact behavior when a capture is already active.

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 coverage is 0%, so the description must compensate. It explains `buffers` with an example ('main,system,crash'), which is real added value. But `clear` (default true) and `serial` (default null for device selection) are left entirely undocumented in both schema and description.

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 a background logcat capture to a temp file.' This clearly distinguishes it from siblings like logcat_dump, logcat_filter, and logcat_stop by role in the lifecycle.

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 names the workflow: read with logcat_dump/logcat_filter, end with logcat_stop, and notes 'Only one capture runs at a time' – a real constraint that governs when to call it. Names alternatives and the condition that selects them.

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