set_dshot_bidir

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

With no annotations, the description must fully disclose behavioral traits. It mentions prerequisites (compile-time defines USE_DSHOT and USE_DSHOT_TELEMETRY) and the default value (OFF), which is helpful. However, it does not specify whether the change takes effect immediately, requires a reboot, or is persisted. It also does not indicate if setting is possible while the flight controller is armed or any side effects.

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 extremely concise: a single clear sentence followed by a parenthetical with technical details. It is front-loaded with the key action and purpose, and every part adds value. No wasted words.

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 its simplicity (single parameter, no output schema), the description covers the main purpose and prerequisites but lacks details on the exact allowed values for the parameter and whether the setting is temporary or persistent. The type mismatch (string vs UINT8) also undermines completeness. Overall, adequate for a basic parameter setter, but not fully comprehensive.

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 input schema describes the 'value' parameter minimally as a string. The description adds the type '(UINT8)', the default 'OFF', and the required compile-time defines. This goes beyond the schema, providing useful semantic context. However, there is a slight contradiction: the schema says 'string' while the description says 'UINT8'; also the allowed values (e.g., ON/OFF or 0/1) are not specified, which could cause confusion.

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 tool's purpose: 'Set dshot_bidir: Enables bidirectional DSHOT for RPM telemetry. Required for RPM filtering.' It identifies the specific action (setting a parameter), the resource (dshot_bidir), and the functional context (RPM telemetry and filtering). This distinguishes it from other set_* tools in the sibling list, as it focuses on a unique parameter.

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 clear context: 'Required for RPM filtering' and a prerequisite ('ESC firmware must support it'). However, it does not explicitly state when to use this tool versus alternatives (e.g., other set_* tools for DSHOT features like set_dshot_burst or set_dshot_bitbang). There is no guidance on when not to use it or which tool to use instead for other DSHOT configurations.

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