list_services

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

With no annotations, the description carries the full behavioral burden, and a single sentence leaves it largely unmet. It implies a read-only listing with no side effects, but says nothing about how the target device is chosen when multiple devices are connected, or about authentication/ADB availability.

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?

A single front-loaded sentence with zero filler. The purpose is delivered immediately and nothing is wasted.

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?

For a simple enumeration tool with an output schema covering return values, the description is minimally sufficient. However, the undocumented 'serial' parameter and the absence of any usage context leave it short of complete for a multi-device ADB toolkit.

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?

There is one parameter ('serial') with 0% schema description coverage, and the description never mentions it. The agent gets no signal that 'serial' selects a specific device when more than one is attached, so the description fails to compensate for the schema gap.

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?

States a specific verb ('List') and resource ('dumpsys service names') with clear scope ('available on the device'). It is easy to distinguish from list_packages, list_processes, and dumpsys, though the description does not explicitly contrast itself with the closely related dumpsys tool.

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 when-to-use guidance is provided. A natural question is when to use list_services versus dumpsys (to dump a specific service), and the description offers no routing between them or any prerequisite on device connection.

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