get_gps_rescue_ground_speed

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

Discloses the data type range [UINT16, 0–3000], default value 750, and a real-world conversion (750 ≈ 27 km/h). No annotations provided, so description carries full burden; it adds useful behavioral context.

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?

Four brief pieces of information in a compact format. Could be slightly more structured, but no wasted sentences. Efficient.

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?

Sufficiently complete for a simple parameter getter. Includes purpose, units, default, range, conversion, and usage tip. No output schema, but return value is implied.

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?

No parameters exist, schema coverage is 100% for the empty schema. The description adds value with unit conversion and range notes, meeting the baseline for zero-parameter tools.

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?

Clearly states the tool gets the forward speed during return with units (cm/s). Distinguishes from the sibling set_gps_rescue_ground_speed as the getter.

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?

Provides specific advice to reduce for reliability in windy conditions, but does not explicitly state when not to use or compare with alternatives. Since it's a simple getter, the guidance is helpful.

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