adb_crash_logs

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

The description states the tool is read-only and returns most recent entries. With no annotations, this is adequate but lacks details on error handling, permission failures, or data format.

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 concise sentences with no unnecessary words. The purpose and key limitation (root access) are front-loaded.

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 tool with 3 params and no output schema, the description covers purpose, access requirements, and behavior. It omits specifics on data format but is largely complete for the use case.

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 100%, so baseline is 3. The description does not add significant meaning beyond the parameter descriptions already present in the schema.

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 states the tool reads ANR traces and tombstone crash dumps, specifying the exact file types. This distinguishes it from siblings like adb_logcat_crash or adb_bugreport, which cover different crash data.

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 mentions root access requirement and directories used, providing essential context for usage. However, it does not explicitly compare with alternatives or advise when to prefer this tool over adb_logcat_crash.

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