toggle_bluetooth

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

Annotations already declare that this is not a read-only operation and is non-destructive, so the safety profile is covered. The description adds that the tool toggles power, but does not clarify whether it requires privileges, what happens if Bluetooth is already in the requested state, or what the response contains.

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 wasted words. It is appropriately sized for a zero-parameter toggle operation.

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 simple zero-parameter toggle with no output schema and clear annotations, the description is largely complete. It could optionally state whether the new state is returned, but that is a minor gap given the tool's simplicity.

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?

The tool has zero parameters, so there is no parameter semantics burden on the description. The baseline score of 4 applies.

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 states a specific verb and resource ('toggle bluetooth power on or off'), making the operation immediately clear. It does not explicitly name sibling alternatives like connect_bluetooth or get_bluetooth_status, but the distinct action is still easy to separate from those tools.

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?

There is no guidance on when to use this tool versus alternatives such as connect_bluetooth, disconnect_bluetooth, or get_bluetooth_status. The implied use case is changing the adapter's power state, but no explicit conditions or exclusions are given.

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