get_serialrx_inverted

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

The description indicates the data type (UINT8) and default value (OFF), adding transparency beyond the empty schema. However, no annotations are provided, so the description should clarify read-only nature; it only implies it's a getter via the name. Side effects and safety are not addressed.

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 repeats the tool name. It mixes the getter action with the parameter's function. Could be more concise by leading with 'Retrieves the serialrx_inverted setting' and removing the redundant name prefix.

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 no output schema, the description should specify what the tool returns (e.g., the current inverted setting). It only mentions the default value and type, but not the actual return value. For a simple getter, this omission reduces completeness.

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 tool has no parameters, and schema coverage is 100%. The description adds context about the parameter's meaning (invert signal, required for receivers), which is useful but not required for parameter semantics. Baseline 4 applies.

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 gets the serialrx_inverted setting and explains the parameter's purpose (invert signal, needed for some receivers). However, it uses the verb 'Invert' which could be confused with the setter action, and doesn't explicitly state it returns the current value.

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?

It mentions the parameter is required for some receivers on certain FC designs, implying when the tool might be relevant, but offers no guidance on when to use this getter versus the setter or related tools (e.g., get_serialrx_halfduplex). No when-not-to-use or alternatives provided.

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