get_gps_update_rate_hz

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

No annotations exist; the description does not disclose behavioral traits like read-only nature, side effects, or authorization requirements. The name implies reading but no explicit confirmation.

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 relatively concise with three sentences and a bracket, but it unnecessarily repeats the tool name. Could be slightly more streamlined.

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 parameters and no output schema, the description covers the purpose, recommends usage, and provides technical context (CPU load impact). It is complete.

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?

Despite having no parameters in the schema, the description adds value by detailing the type (UINT8), range (1-20), and default (10) in brackets, exceeding the baseline.

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 the tool gets the target GPS update rate, and distinguishes it from sibling tools by focusing on this specific parameter. It includes context about recommended values for GPS rescue and CPU load reduction.

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 usage guidance (10 Hz for GPS rescue, 1-2 Hz otherwise) with rationale (CPU load, 8k8k). Lacks explicit when-to-use vs. alternative getters, but the context is strong.

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