adb_ril_poll

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

Without annotations, the description gives some behavioral context (cumulative since last poll, optional parsed vs raw) but does not disclose important traits like destructiveness, concurrency limits, or the effect on captured messages post-poll. Adequate but not thorough.

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 sentences, each carrying distinct value: the first states the core action, the second adds optional filtering. No redundancy or fluff.

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?

Given the tool's simplicity and schema coverage, the description adequately covers purpose and filtering. However, it does not explain the return format (e.g., list of messages) despite no output schema, and assumes familiarity with session setup.

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 3. The description adds minimal value beyond the schema; it lists categories but omits 'sms' and 'other' present in the schema. The description of raw and maxMessages is not enhanced.

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 clearly states the tool retrieves captured RIL messages since the last poll, with an optional category filter. It uses specific verbs and distinguishes from siblings like adb_ril_start (which initiates capture) and adb_logcat_poll (which polls logcat).

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 implies usage after adb_ril_start but provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or when not to use it.

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