set_blackbox_mode

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

With no annotations, the description should cover behavioral traits. It only lists values and default, omitting potential side effects, required disarm state, or impact on existing logging. The description is incomplete for a mutation tool.

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 sentence with additional details in brackets. It is concise and front-loaded, though the parameter info is somewhat jammed together.

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 setter with one parameter and no output schema, the description covers the essential values and default. However, it omits prerequisites (e.g., status of flight controller) and potential consequences, which would be helpful for safe usage.

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 schema describes 'value' as UINT8, but the description adds the acceptable string values (NORMAL, ALWAYS, MOTOR_TEST) and default. This adds meaningful context beyond the schema's brief description.

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 explicitly states it sets the blackbox mode and enumerates the three possible values (NORMAL, ALWAYS, MOTOR_TEST) with clear explanations. This distinguishes it from get_blackbox_mode and other set 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?

The description provides no guidance on when to use this tool versus alternatives or prerequisites. The agent is left to infer from context that one would set the mode before or after configuring other blackbox settings.

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