set_sbus_baud_fast

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

Without annotations, the description carries the full burden. It discloses the data type (UINT8) and default value (OFF), but does not mention side effects (e.g., requires receiver support, may need reboot), validation, or behavior when set incorrectly. This is minimal but non-contradictory.

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: one action sentence, a condition, and a type/default note. No fluff, front-loaded with the core action.

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 set tool with a single parameter and no output schema, the description provides the essential purpose and condition. However, it lacks details on valid value range, error handling, and whether a reboot is required, leaving some gaps for an agent.

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 coverage is 100%, so baseline is 3. The description adds context by tying the parameter to the fast mode enablement and noting the type and default, but does not specify valid values or format beyond what the schema already describes.

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: to set/enable fast (200kbps) SBUS mode. It specifies the target resource (sbus_baud_fast) and condition (for SBUS receivers that support it), distinguishing it from the corresponding getter and other configuration 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 context on when to use this tool (for compatible SBUS receivers) but does not explicitly mention alternatives or when not to use it. It lacks direct comparison with the getter (`get_sbus_baud_fast`) or other serial configuration tools, but the condition is helpful.

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