adb_thermal_compare

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

The description discloses that the tool compares current state against a baseline and reports differences, which implies a read-only operation. However, it does not explicitly state whether there are any side effects, authorization requirements, or limitations (e.g., frequency of use). Without annotations, the description should be more 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 very concise, consisting of just two sentences that clearly convey the tool's purpose and output. No extraneous information is included.

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 the tool has no output schema and two optional parameters, the description provides sufficient context for basic usage, explaining the comparison and the type of output reports. However, it could be improved by mentioning how to create a baseline or what happens if no baseline exists.

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 covers 100% of the two optional parameters with clear descriptions. The tool description adds minimal extra value beyond the schema, only mentioning 'saved baseline' which is already implied. No further parameter semantics are provided.

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 that the tool compares current thermal/power state against a saved baseline and lists the specific reports it generates (temperature changes, CPU frequency shifts, battery drain rate differences). However, it does not explicitly distinguish itself from sibling tools like adb_thermal_snapshot or adb_battery_drain, which could lead to confusion.

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 is provided on when to use this tool versus alternatives. The description implies a baseline must exist (either saved or most recent), but it does not state prerequisites, such as requiring a prior baseline capture via adb_thermal_snapshot.

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