adb_thermal_snapshot

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

With no annotations, the description should disclose behavioral traits. It only lists captured data but omits whether it is read-only, requires root, or has side effects. The info is incomplete for safe agent invocation.

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, clearly structured, and contains no unnecessary words. Every phrase adds value and is 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?

The description lists captured data but does not mention the output format (e.g., JSON, console). Since there is no output schema, the agent could benefit from knowing how to interpret results. Also, the device parameter is left unexplained in the description.

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?

Input schema has 100% description coverage for all 3 parameters, so the schema already explains each parameter. The description adds minimal extra meaning beyond listing what can be captured. Baseline 3 is appropriate.

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 captures a thermal and power snapshot with specific data (thermal zones, CPU frequencies, battery info). It distinguishes from siblings like adb_battery or adb_perf_snapshot by focusing on thermal and power details.

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 implies use for detailed thermal/power diagnostics but does not explicitly state when to use this vs. alternatives like adb_thermal_compare or adb_battery. No when-not or prerequisite guidance is provided.

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