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

With no annotations provided, the description carries the full burden and delivers richly: it discloses that the tool enables Runtime and Log domains, listens for three specific events, returns a normalized array, is a live-window collector that only captures post-attach events, has a ~1-3s attach latency race condition, and supports pageId auto-selection. This is exemplary behavioral disclosure.

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 dense (~130 words) but every element is load-bearing: the live-window warning and triggerJs guidance are critical for correct use. It is front-loaded with the core purpose. Minor redundancy exists between the main race warning and the triggerJs parameter description, so it is not maximally tight, but it is well-structured.

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 5-parameter tool with 100% schema coverage and no output schema, the description is complete: it documents the return shape ({ level, text, url?, lineNumber? }), the live-window semantics, defaults, maximum, and page auto-selection. There is no output schema and no annotations, yet the description covers everything an agent needs to call it 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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by explaining that triggerJs runs INSIDE the collection window and is race-free, gives concrete examples ('location.reload()', 'console.log('probe')'), and cross-references the default/max window values that the schema also encodes. This meaningfully enriches parameter understanding, warranting a 4.

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 states a specific verb and resource: 'Collect console logs, exceptions, and log entries from a page running on the device for a time window.' It further distinguishes itself by naming the exact CDP domains and events (Runtime.consoleAPICalled, Runtime.exceptionThrown, Log.entryAdded) and the normalized return shape, which clearly separates it from siblings like android_devtools_capture_network, session_console_logs, and web_console_messages.

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 gives explicit when-not guidance: triggering logging from a SEPARATE tool call 'races the ~1-3s attach latency and is silently missed,' and provides the corrective alternative: 'pass triggerJs (runs inside the window).' It also states the default (3000 ms), maximum (15000 ms), and page auto-selection behavior, leaving no ambiguity about how to invoke it correctly.

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