list_dev_apps

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

With no annotations present, the description carries the full load and does disclose the most important behavioral trait: the result is filtered to debuggable, testOnly, adb-installed builds, so it is not an enumeration of all installed apps. It does not say whether the call is read-only or what happens on a device that permits none of these builds, which are minor remaining gaps.

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 short sentences, front-loaded with the verb and resource, then the eligibility constraint. No filler, though the 'Android Studio (Run)' parenthetical phrasing is slightly dense compared with simply saying 'debuggable and testOnly'.

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 one-optional-param read-only listing tool with no output schema, the definition covers what is listed and what qualifies. It stops short of describing returned fields or multi-device behavior, but an agent can call it correctly with what is here.

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 coverage is 100% and the single optional serial parameter is fully documented in the schema, so the schema does the work. The description adds nothing about serial or multi-device selection; baseline 3 applies.

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 (apps this server may use), and the second sentence narrows it to debuggable + testOnly builds installed via adb, so an agent can tell it apart from current_app or launch_app. The name is a little ambiguous (dev apps vs. all installed apps) but the description resolves it.

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?

The criterion for inclusion is given, which implies 'use this to discover which apps are launchable', but there is no explicit when-to-use/when-not framing or reference to a sibling such as current_app or launch_app. Usage is inferred rather than stated.

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