get_gps_set_home_point_once

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It explains the effect of the setting but does not state that this is a read-only operation with no side effects. The agent must infer safety from the 'get' prefix; no explicit mention of read-only or non-destructive behavior.

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 exceptionally concise, consisting of two short sentences and a brief type/default annotation. It is front-loaded with the tool's purpose, and every word adds value. No extraneous 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?

Given no output schema and no parameters, the description adequately covers the tool's purpose and the setting's impact. It explains the behavioral nuance of the setting (first arm only). However, it does not describe the return format or potential values beyond the default hint.

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 input schema has zero parameters, and schema description coverage is 100%. With no parameters, the baseline is 4. The description does not need to explain parameters. The type and default are noted in brackets, adding clarity.

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 that this tool retrieves the current setting of 'gps_set_home_point_once', and explains the setting's behavior: only sets home point on first arm after battery connect, preventing reset if disarmed/re-armed mid-field. This is specific and distinguishes it from the sibling 'set_gps_set_home_point_once' tool.

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 explains what the setting does, implying the tool is used to check the current configuration. However, it does not explicitly state when to use this getter versus alternatives, such as the setter tool or other GPS-related tools. No direct usage scenario or exclusion is provided.

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