set_gps_use_3d_speed

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

No annotations are provided, so the description must carry behavioral disclosure. It only mentions data type (UINT8) and default (OFF), but does not describe side effects, persistence, whether a reboot is required, or what happens if an invalid value is provided. For a simple setter, this is minimal.

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 a single concise sentence. It is not overly long, though it redundantly repeats the tool name. No unnecessary information, but could be slightly improved by removing redundancy.

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?

The tool is a simple setter, and the description explains its purpose and default. However, it does not specify the expected value format (e.g., numeric string '0' or '1', or 'ON'/'OFF'), nor any constraints. With no output schema, more detail on what to expect after setting could improve 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?

Schema description coverage is 100% (one parameter described as 'Value for gps_use_3d_speed (UINT8)'). The tool description adds that the default is OFF, but does not clarify the expected format (e.g., numeric string like '1' or '0') or range. Baseline 3 is appropriate as the description adds minimal value beyond the schema.

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 the action ('Set') and the specific resource ('gps_use_3d_speed'). It explains the purpose: use 3D speed (including vertical) for GPS speed display. This distinguishes it from unrelated set_* tools and the sibling get_gps_use_3d_speed.

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 lacks guidance on when to use this tool versus alternatives. It does not explain when 3D speed is preferable to 2D speed, nor does it mention that one might first check the current value via get_gps_use_3d_speed. No prerequisites or when-not-to-use are provided.

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