ble_drain_notifications

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

No annotations are provided, so the description carries the full burden. It clearly explains the iterative collection behavior with three stopping conditions (idle_timeout, max_items, timeout_s). The behavior is transparent, though it omits any side effects or permissions.

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 two sentences with the key behavior in the first sentence and a use-case example in the second. No fluff; every word serves a purpose. It is front-loaded and easy to parse.

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 explains the collection logic and stopping conditions, but it does not specify the return value format (e.g., array of notifications) or error handling. Given no output schema, this is a notable gap, though the tool is relatively simple.

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 60%, but the description adds context by explaining how the parameters interact (wait for first, then idle or max or total timeout). This adds meaning beyond the individual field descriptions, especially for the time and count parameters.

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 'batch-collect notifications' and details the collection logic (waits for first, then collects until idle_timeout, max_items, or timeout). It implies a difference from single-notification tools like ble_wait_notification but does not explicitly distinguish from siblings like ble_poll_notifications.

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 suggests use for 'bursty flows' like downloading datasets, providing context. However, it lacks explicit guidance on when not to use this tool or comparison to alternatives (e.g., ble_wait_notification for single notifications, ble_poll_notifications for polling).

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