get_rssi_scale

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

No annotations provided, so the description should disclose traits like whether this reads from the flight controller or config, or if it returns a cached value. It only states the type and default, lacking behavioral context.

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 short (one sentence plus a bracketed note), which is concise but lacks structure. It front-loads the name but provides minimal detail, making it adequate but not well-organized.

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?

There is no output schema, so the description should explain the return value's meaning and format. While it mentions UINT8 and default, it does not describe how the scale is used (e.g., multiplier applied to raw RSSI) or any units. Incomplete for a parameterless tool.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds value by specifying the return type (UINT8) and default (100), which helps interpret the output.

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 it retrieves the RSSI scale and specifies the data type (UINT8) and default value (100). The purpose is clear as a getter for a scaling parameter, but could be more explicit about the role of the scale (e.g., multiplier for RSSI readings).

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 other getters or the related set_rssi_scale. The description does not differentiate it from the many siblings or explain prerequisites.

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