adb_logcat_poll

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

No annotations provided, so description carries full burden. 'Since the last poll' hints at statefulness but does not explain behavior if session is missing or stopped, whether it is blocking, or rate limits. Lacks key behavioral details.

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?

Single sentence, 14 words, very concise. Front-loaded with core purpose. Could benefit from slightly more structure (e.g., bullet points) but not wasteful.

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?

Missing context about session lifecycle (must be started via adb_logcat_start), return format (just lines or structured?), and error handling (invalid session). No output schema compensates for return format. Incomplete for new users.

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% with clear parameter descriptions. The tool description adds no additional meaning beyond what's already in the schema, so baseline score of 3 is appropriate.

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 clearly states the action (retrieve new logcat lines) and the specific resource (from a running watcher session), distinguishing it from sibling tools like adb_logcat (full dump) or adb_logcat_start (session management).

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?

Implies use after adb_logcat_start, but no explicit when-to-use or when-not-to-use. No alternatives mentioned despite many related siblings (adb_logcat_start, adb_logcat_stop, etc.).

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