get_anr_traces

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

With no annotations, the description carries the full burden. It usefully discloses the root/permission requirement and the return shape, but says nothing about whether an existing local file is overwritten, transfer size limits, or what happens when no trace exists.

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 tight sentences with no filler, front-loading the action and the exact file paths before the caveat. 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?

An output schema exists, so return-value detail is optional (the description duplicates some of it anyway). The real gap is that a 2-parameter tool with zero schema coverage and no annotations leaves the agent without parameter guidance, making the definition only minimally complete.

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 0% and the description never mentions either parameter. Neither 'serial' (device targeting) nor 'local_path' (destination) is explained; the mention of 'local' in the return object only hints at the latter. The description does not compensate for the coverage gap.

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?

Specific verb ('Pull') plus a precisely named resource ('most recent ANR trace file') with concrete paths (/data/anr/traces.txt or /data/anr/). This clearly separates it from siblings like get_crash_log, capture_bugreport, or logcat_dump.

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?

Usage is only implied by the resource name (ANR diagnostics); there is no explicit when-to-use guidance, no mention of when to prefer it over get_crash_log or capture_bugreport, and no stated prerequisites beyond a parenthetical about root.

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