set_gps_ublox_flight_model

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

No annotations are provided, so the description carries the full burden. It states the tool sets the model and notes the default, but it does not disclose potential side effects, such as whether a reboot is required or if GPS must be active. Mutation is implied but not explicitly stated as safe or 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 concise with two sentences. It front-loads the purpose and key details, with no unnecessary information.

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, default, and an example. However, it does not enumerate all possible dynamic model values, which could help an agent choose the correct input. Overall, it is fairly complete but missing parameter options.

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 single 'value' parameter has 100% schema description coverage. The description adds the default value ('AIRBORNE_4G'), explains it as 'UINT8', and provides an example, giving significant meaning beyond the schema alone.

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 the UBlox dynamic model used during flight. It provides the specific value 'AIRBORNE_4G' and explains its use case for high-dynamics FPV. Among siblings, it is distinct from other set_gps_ublox_* 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 mentions 'AIRBORNE_4G handles high-dynamics FPV' which implies usage context, but it does not explicitly state when to use this tool versus alternatives, nor does it provide conditions or prerequisites.

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