get_gps_use_3d_speed

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

With no annotations, the description carries the burden for transparency. It indicates the tool is a getter (read-only) and notes the data type (UINT8) and default (OFF). However, it fails to explain what the returned values represent (e.g., 0=OFF, 1=ON) or any side effects.

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 with two sentences and a bracketed note. It front-loads the action and includes all essential information without any wasted words.

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 getter with no output schema, the description is adequate but could be improved by specifying the return format (e.g., integer value) or mentioning that it returns the current setting. Given the lack of output schema, some additional context would help.

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 no parameters, so the description does not need to add parameter details. Schema coverage is 100%, and the description appropriately mentions the data type and default value, providing sufficient context.

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 'Get' and the resource 'gps_use_3d_speed', with a brief explanation that it retrieves whether 3D speed is used. It distinguishes from the sibling 'set_gps_use_3d_speed' tool, but does not differentiate from other similar getters.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that this is a read-only operation or suggest checking this before setting, nor does it list any prerequisites or exclusions.

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