get_gps_auto_config

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

No annotations are provided. The description adds context about the default value ('default: ON') and data type ('UINT8'), but does not explicitly state that this is a read-only operation. However, the 'get_' prefix strongly implies read-only, so the lack of explicit safety info is acceptable.

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?

Two concise sentences plus a compact bracketed note. Every word adds value: the action, the setting's purpose, usage advice, and default value. No waste.

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 adequately explains the setting's role and default. It could optionally mention the valid range (e.g., 0 or 1) or the return value format, but this is not essential for selection.

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 tool has zero parameters, and the schema covers 100% of them. The description does not need to add parameter details. According to calibration rules, baseline score for 0 parameters is 4.

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 tool retrieves the GPS auto-config setting for UBlox modules. It explains what the setting does (configure baud rate, update rate, message types) and distinguishes it from other GPS-related tools like get_gps_auto_baud or set_gps_auto_config.

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 a clear guideline: 'Leave ON unless you pre-configure the module with uCenter.' This helps the agent understand when to keep the setting enabled. No explicit alternatives are needed since it's a simple getter.

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