flush_device_downlink_queue

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

With no annotations, the description should provide behavioral context. It accurately indicates a destructive operation ('Delete all pending'), but does not disclose if it is reversible, requires specific permissions, or affects other aspects like device state.

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 a single, concise sentence with no superfluous information, making it easily digestible.

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 (1 required param, no output schema), the description adequately conveys the core action. Could be slightly more complete by noting that only pending items are affected, but overall sufficient.

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?

Parameter 'dev_eui' has no schema description (0% coverage), and the description only vaguely implies its purpose by mentioning 'for a device'. It adds minimal meaning beyond the parameter name.

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 verb 'Delete' and the resource 'all pending downlink items for a device', distinguishing it from siblings like 'enqueue_device_downlink' and 'flush_multicast_downlink_queue'.

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 use for clearing a device's downlink queue, but lacks explicit guidance on when to use vs alternatives like 'get_device_downlink_queue' or 'enqueue_device_downlink'.

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