set_gps_set_home_point_once

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

With no annotations, the description carries full burden. It explains the effect (only set on first arm, prevents reset) and notes the default is OFF. However, it does not disclose prerequisites (e.g., GPS fix required), side effects, or behavior of ON vs OFF beyond the basic description.

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 extremely concise: two sentences plus a type/default note. Every word adds value, and the most critical information (action and behavior) 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 and no output schema, the description covers the core purpose and effect. However, it does not specify the expected value format or range, and omits details about the return value or confirmation of the setting.

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 schema has 100% coverage but the description contradicts it by stating 'UINT8' while the schema defines the parameter as a string. The description does not clarify acceptable values (e.g., 0/1 or ON/OFF) beyond the default, and lacks format guidance for the string input.

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 a GPS home point parameter to only set home on first arm after battery connect. It explains the behavioral effect and distinguishes from other set_ tools by specifying the unique behavior of preventing home reset on disarm/re-arm.

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 clear context for when to use this tool (to limit home point setting to first arm) and implies the default behavior is different. However, it does not explicitly state when not to use it or compare with alternatives like other GPS home point settings.

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