Read a logcat snapshot

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so safety is covered. The description adds real behavioral context beyond that: it captures a bounded snapshot (not a follow), is scoped to one device, and the output is bounded — the key trait separating it from the stream tools.

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 sentences, zero waste: behavior and scope first, then the routing constraint. Everything is front-loaded and every clause 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?

For a read-only snapshot tool with 100% schema coverage and full annotations and no output schema, the description covers the essential decision (snapshot vs stream) and the bounded nature of output. It need not enumerate return format, though a note on truncation behavior would close the remaining gap.

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 all four parameters (device, max_lines, timeout_ms, filter_spec) are already documented in the schema; baseline 3 applies. The description's phrase 'optionally filtered to a log tag' is slightly narrower than the schema's full logcat filter spec, adding little and potentially under-selling filter_spec.

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 ('Dump the current logcat buffer') plus the underlying command and scope ('from one device'), and explicitly sets itself apart from the streaming siblings. An agent can tell it apart from start_logcat_stream/read_logcat_stream without opening any schema.

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?

'use the stream tools when you need to watch logs over time' gives a clear selection condition and points to the alternative family. It stops short of naming the exact sibling (start_logcat_stream vs read_logcat_stream) or stating the reverse condition, so it is clear but not fully explicit.

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