adb_ril_start

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

With no annotations provided, the description carries full burden. It discloses the types of captured events but omits critical behavioral details: whether it returns immediately or runs in background, how to stop (sibling adb_ril_stop is not mentioned), resource consumption, or lifecycle of the capture. The bufferSize parameter hints at a ring buffer but is not explained.

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 three concise sentences, each adding value: first states the action, second details captured events, third notes use case. No fluff or repetition.

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?

Although the description lists captured events, it does not explain the tool's lifecycle (e.g., whether it starts a persistent capture or returns immediately) or how to retrieve captured data. Without an output schema, more context is needed for an agent to use the tool effectively alongside siblings.

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 does not add any additional meaning to the parameters beyond what the schema already provides. It lists captured events but does not relate them to parameters like includeKernel.

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 starts capturing RIL messages, lists specific events (network registration, cell info, etc.), and states the use case (radio diagnostics and research). It distinguishes itself from siblings like adb_ril_stop and adb_ril_poll by emphasizing the start action.

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 the tool is used for starting RIL capture for diagnostics, but does not explicitly state when to use it vs. alternatives (e.g., before adb_ril_poll) or when not to use it. No prerequisites or context are mentioned.

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