device_deactivate

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

Annotations already indicate destructiveHint=true, and the description adds specific behavioral context: the session is dropped and the device must re-join to communicate again. This goes beyond the annotation by explaining the operational consequence.

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, front-loaded sentence with no filler. It states the action and its key consequence efficiently.

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?

For a single-parameter destructive operation with an output schema and destructive annotation, the description covers the essential behavior and consequence. It is slightly incomplete because it omits explicit usage guidance, but the operation is simple enough that the information provided is largely 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?

Schema description coverage is 0% for the dev_eui parameter, and the description does not mention the parameter or explain how to identify the target device. While 'dev_eui' is a self-explanatory parameter name, the description provides no compensatory semantic guidance.

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 and resource: 'Drop the device session,' and clearly states the consequence that an OTAA device must re-join before communicating. This distinguishes it from siblings like device_delete and device_activate without ambiguity.

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 usage scenario: deactivating a device to force a re-join. However, it does not explicitly state when to prefer this over alternatives such as device_delete or device_activate, and it does not address how non-OTAA devices are affected.

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