adb_logcat

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation (dump recent lines) but doesn't disclose whether this requires specific device permissions, what the output format looks like, or how the 'recent' window is determined (ring buffer size, etc.). For a benign read-diagnostic tool this is moderately adequate but not rich.

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 sentence with zero wasted words. 'Dump recent logcat lines (optionally grep-filtered)' is compact, front-loaded with the action, and adds the key optional behavior in a parenthetical. It's appropriately brief for a simple diagnostic tool.

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 diagnostic tool with only 3 optional parameters and no output schema, the description is mostly sufficient. However, it doesn't clarify the interaction between 'lines' and 'filter' (whether filtering applies before or after the line limit), which is a meaningful operational detail an agent would need when invoking with both parameters. The absence of a device-requirement note is also a small gap but not critical.

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 only 33% (only 'serial' has a description). The description adds meaning by explaining 'filter' as a 'grep-filter' for logcat output, and 'lines' as the count of recent lines. This goes beyond the schema, though the 'filter' parameter's format/recipe with 'lines' (does filtering happen before or after truncation?) could be clearer.

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 states a clear verb+resource ('Dump recent logcat lines') and mentions the grep-filtering option, which gives a clear sense of what it does. However, it doesn't explicitly distinguish it from sibling tools like adb_shell (which could also be used to run logcat) or other adb diagnostic tools.

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 explicit when-to-use guidance or exclusions are provided. The description implies usage for reading logcat output but offers no direction on when to prefer this over adb_shell, or any caveats about device requirements, buffering, or alternative diagnostic tools.

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