adb_ril_poll

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

With no annotations, the description carries the full burden. It explains retrieval and filtering but does not disclose whether polling is destructive (clears buffered messages), what happens if the session is invalid, or the format of returned data. The 'since last poll' hint is useful but incomplete.

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?

A single sentence with a parenthetical list conveys the core function and main option concisely. There is no redundancy or extraneous information.

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?

The description covers the basic purpose and one key parameter (category). However, it lacks details about return values, error handling, and the relationship between polling and the session lifecycle. The schema covers parameter details, but without output schema, additional context would be beneficial.

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 the schema already documents all parameters. The description adds value by listing category options in text, but this duplicates the schema's description. The meaning of session, maxMessages, and raw is clear from the schema.

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 uses a specific verb ('Retrieve') and resource ('RIL messages'), and clearly states the scope ('since the last poll'). It also mentions optional filtering, distinguishing it from sibling tools like adb_ril_start and adb_ril_stop.

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 polling behavior but does not explicitly state when to use this tool vs alternatives, nor does it mention prerequisites like starting a session with adb_ril_start. No exclusions or when-not guidance is provided.

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