get_sbus_baud_fast

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

No annotations are provided, so the description must disclose behavior. The description mentions it is for SBUS receivers that support fast mode, but does not indicate that it is a read operation (retrieving the current setting), nor does it describe the return value. The conflicting verb 'enable' may mislead about its 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 short but contains contradictory and extraneous information (e.g., parameter type/default without schema support). It is not structured clearly.

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 get tool with no output schema, the description should explain what the returned value represents. It does not, leaving the agent without information about the output format or possible values.

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 description includes '[UINT8, default: OFF]', implying a parameter exists, but the input schema has no properties (0 parameters). This contradicts the schema. Since schema coverage is 100% (empty), the description should not introduce non-existent parameters.

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 'Get sbus_baud_fast: Enable fast (200kbps) SBUS mode.' This is contradictory: the tool name suggests a read operation ('get'), but the description describes it as enabling (a write operation). The purpose is unclear and potentially misleading.

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?

No guidance on when to use this tool versus alternatives like the sibling 'set_sbus_baud_fast'. The description implies a specific use case (SBUS receivers that support fast mode) but does not clarify that this is a read operation.

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