adb_thermal_snapshot

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

Discloses exactly what data is captured (thermal zones, CPU states, battery) and the optional save feature. With no annotations, the description effectively conveys a read-only, non-destructive snapshot. Could mention if any side effects exist, but overall strong.

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 succinct sentences: first states the core action and data collected, second explains optional saving. No redundant information; front-loaded for quick comprehension.

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?

Given no output schema or annotations, the description is largely complete: it specifies inputs, outputs (implicitly the snapshot data), and optional save behavior. Could mention return format, but sufficient for most agents.

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 the schema already documents parameters. Description adds context for 'save' and 'label' (saving as baseline) but doesn't elaborate on 'device'. 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?

Description clearly states the tool captures a thermal and power snapshot with specific data points (thermal zones, CPU frequencies, etc.). This distinguishes it from siblings like adb_perf_snapshot or adb_thermal_compare.

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?

No explicit guidance on when to use this tool vs alternatives, such as adb_thermal_compare or adb_battery. Usage is implied for thermal monitoring but lacks exclusions or context.

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