adb_get_logcat

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

No annotations are present, so the description carries the behavioral disclosure burden. It communicates a read-style retrieval operation and the filtering/limiting behavior, but it does not explicitly state that it is non-destructive, what the output format looks like, or whether a device connection is required.

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 the core action first and all optional modifiers in one clear clause. There is no filler, redundancy, or unnecessary background.

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 simple read-style logcat tool with three optional parameters and no output schema, the description gives enough context to select and invoke it. It is slightly light on output format and explicit alternative routing, but those gaps are minor for this complexity level.

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 the schema already documents all parameters. The description only restates the filtering dimensions (tag, log level, latest N lines) without adding defaults, formats, or constraints beyond what the schema provides.

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 ('Obtiene') and a concrete resource ('buffer de logcat del dispositivo Android'), and mentions the optional filters. This makes it clearly distinct from siblings like adb_clear_logcat or adb_dump_hierarchy even without naming them.

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 clearly implies logcat retrieval ('obtiene el buffer de logcat'), so an agent can infer when to use it. However, it does not provide explicit guidance about when not to use it or how it compares to alternatives such as adb_clear_logcat.

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