adb_crash_logs

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

No annotations are provided, so the description carries the burden. It discloses root access requirement and returns most recent entries, but does not mention potential errors or if data is modified. The read-only nature is implied, not explicit.

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 two sentences with essential information: purpose, prerequisite, and behavior. It is front-loaded and contains no redundant text.

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?

With no annotations and no output schema, the description covers purpose, requirements, and basic behavior. However, it does not describe the format of returned entries (e.g., timestamps, stack traces), leaving some gaps for an agent.

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?

The input schema has 100% coverage with clear descriptions for type, maxEntries, and device. The description adds context about file paths but does not significantly enhance parameter understanding beyond schema defaults.

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 it reads ANR traces and tombstone crash dumps, specifying the resource (device crash logs). It distinguishes from sibling tools like adb_logcat or adb_heap_dump by targeting specific crash file types.

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 but does not explicitly compare to alternatives like adb_logcat for general logging. No when-not-to-use guidance is provided, but the purpose implies when to use it.

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