adb_mobile_data

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action without revealing side effects, required permissions, or potential limitations (e.g., device compatibility, root requirements). The tool likely mutates device state, but this is not stated.

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 one sentence of five words, which is concise but lacks necessary elaboration. While every word earns its place, the brevity sacrifices completeness. It is neither verbose nor optimally informative.

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 (boolean toggle, two params, no output schema), the description is minimally viable. However, it does not mention that the operation may fail on non-rooted devices or that the device parameter is optional. Slight gaps remain for full completeness.

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 baseline is 3. The description adds no extra meaning beyond the schema; it essentially restates the 'enabled' parameter's schema description. The 'device' parameter is not elaborated further.

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 'Enable or disable mobile data' uses a specific verb and resource, clearly indicating the tool's function. It distinguishes from siblings like adb_airplane_mode and adb_network by specifying mobile data specifically.

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 guidance on when to use this tool versus alternatives such as adb_airplane_mode or adb_network_auto_connect. There is no mention of prerequisites, conditions, or alternatives, leaving the agent without decision criteria.

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