adb_location

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

The description only states that it enables or disables location services, which implies mutation. However, it does not disclose any side effects (e.g., requiring permissions, affecting battery life, or persistence of changes). Without annotations, the description carries the full burden of behavioral disclosure, which it fails to meet.

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 a single sentence, which is concise but too sparse. It front-loads the core action but lacks essential details that would fit within a concise format.

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's simplicity (2 parameters, no output schema), the description is adequate but not complete. It covers the basic purpose but omits important context like what each mode does in practice or how the tool interacts with system settings.

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?

With 100% schema description coverage, the schema already defines the parameters (mode with enum values and device serial). The description adds no additional meaning beyond 'enable or disable,' so it meets the baseline but does not enhance understanding of parameters.

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's function: to enable or disable location services. It uses a verb-resource structure that distinguishes it from sibling tools like adb_gps_firmware or adb_network, as it specifically targets location mode settings.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, nor does it mention prerequisites like device connectivity or which mode is appropriate for different scenarios.

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