set_crsf_use_negotiated_baud

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the effect (allows baud rate negotiation) and default value, but does not mention whether the change is immediate or requires a reboot, what happens if set incorrectly, or any side effects. For a flight controller parameter, such details are critical.

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 very concise: one sentence stating purpose, one sentence with usage context, and a bracketed type/default. No wasted words. Essential information is front-loaded.

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, the description covers purpose and usage scenario. However, it lacks explicit mention of acceptable values (0/1) and whether a reboot is needed. Given the context of many similar set_* tools, this is adequate but not thorough.

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 provides a generic description for the 'value' parameter. The description adds useful context: it clarifies the type (UINT8) and the default (OFF), which guides the agent on acceptable input format. This adds value beyond the schema.

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 it sets 'crsf_use_negotiated_baud' to allow CRSF to negotiate baud rate. The verb 'Set' and resource name are explicit. However, it does not differentiate from other set_* tools beyond the parameter name, which is already clear from the tool name.

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 a specific usage context: 'Enable when using faster CRSF rates (e.g. ELRS negotiated speed).' This tells the agent when to use this tool. It does not mention when not to use it or alternatives, but for a simple setter this is acceptable.

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