adb_sensor_read

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

Discloses that it returns last-known readings with timestamps, is device-dependent, and requires no root. No annotations provided, so description covers behavioral traits adequately without contradiction.

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 sentences, front-loaded with the core action, no redundant information, every sentence adds value.

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 output schema, the description hints at output (readings with timestamps). Covers essential behavior for a read tool, though could detail output format more.

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 100%, so the schema already details parameters. The description adds no additional meaning beyond stating the tool returns readings with timestamps, which is baseline for high coverage.

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?

Clearly states the tool reads current hardware sensor values, enumerates all available sensors, and returns last-known readings with timestamps. Distinguishes from siblings like adb_iio_read by focusing on sensorservice.

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?

Provides context that sensor availability is device-dependent and no root required, but does not explicitly guide when to use this tool over alternatives or mention any prerequisites or constraints.

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