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

With no annotations provided, the description carries the full disclosure burden and meets it thoroughly. It discloses the returned fields, newest-active-first ordering, the special meaning of 'active: true', the WebView-only nature of 'visible', and the caveat that stale tabs accumulate across sessions.

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?

Every sentence earns its place: each adds behavioral or usage guidance rather than repeating structured data. The main action is front-loaded, and the longer explanatory notes about 'active', 'visible', and stale tabs are placed after the core purpose, making the description dense but well-organized.

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 list-only tool with no output schema and no annotations, this description is complete. It specifies returned fields, ordering, default-target semantics, and a cleanup path, while the two parameters are fully covered by the schema. An agent has everything needed to call this tool correctly.

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 baseline is 3. The description does not add extra meaning about 'udid' or 'socket' beyond the schema, but the schema already documents both parameters, so no critical semantic information is missing.

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?

Description begins with a specific verb and object: 'List debuggable pages/targets available on the device.' It enumerates returned fields and clearly frames the tool as an enumeration action, distinguishing it from sibling DevTools commands like android_devtools_close_page. The purpose is unmistakable and immediately actionable.

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 description explicitly tells agents when listing is unnecessary: 'you do NOT need to list tabs and pass an id just to act on the current tab, only to act on a DIFFERENT one.' It also names android_devtools_close_page as the tool for cleaning stale tabs, providing an actionable alternative and clear usage boundary.

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