ble_poll_notifications

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

Discloses all key behaviors: non-blocking, returns up to max_items, empty list if queue empty, and dropped counter for overflow. No annotations exist, so description carries full burden and does well.

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 with no wasted words. Front-loaded with the most important trait (non-blocking) and explains behavior clearly.

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 no output schema, description explains return values (list and dropped counter) and behavior. Sibling tools exist for blocking and drain variants, so this description is complete for an agent to pick correctly.

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?

Only max_items has a schema description (33% coverage). Description adds default and max for max_items but does not explain connection_id or subscription_id. With low coverage, description should provide more context for all params.

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?

Clearly states it is non-blocking, returns buffered notifications immediately, and provides a dropped counter. Distinguishes from siblings like ble_wait_notification (blocking) and ble_drain_notifications (drain all).

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?

Mentions non-blocking behavior, implying it's for polling without waiting. However, does not explicitly state when to use over alternatives like wait_notification or drain_notifications.

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